wait a sec. there are two distinct set of "problems". One is avoiding using reserved keywords, that is a "bad choice" in respect of what usually are "verbs" in t-sql dialects. in this matter, the check_reserved argument deals with (most of) them avoiding to create some table or some field named "xxx" if the "xxx" is a reserved keyword in t-sql dialects. Then there is quoting. This is "solved" by using rname, that basically deals with quoting all entities (tables and fields) to avoid treating those "verbs" as verbs, and instead correctly signalling it's an entity. Here is probably where there's the "short-circuit" you're experiencing (I'd say a bug, but needs testing). If you're already quoting correctly entities, then the "check_reserved" argument should not alert you that you're using an entity name that is a "verb".
Is this more clear ? On Monday, July 21, 2014 6:32:33 PM UTC+2, Simon Ashley wrote: > > Thanks but basically, all we're trying to do is to specifically map the > DAL field name to the name as stored in the database, and ascertain why our > original scenario/ approach fails. > (reserved names maybe only a subset of issues we're trying to avoid. > Have a feeling that a QUOTE_TEMPLATE solution may turn out to be > inflexible. I think we are at cross purposes). > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
