Yes, I decided to just have like POSTGRES for reserved words and POSTGRES_NONRESERVED, so you can check both if you so desire.
To check nonreserved keywords as well then just append _nonreserved after the adapter name check_reserved = ['postgres', 'postgres_nonreserved'] -Thadeus On Fri, Feb 5, 2010 at 6:23 AM, villas <villa...@gmail.com> wrote: > On 5 Feb, 03:19, Thadeus Burgess <thade...@thadeusb.com> wrote: >> A quick question, what is your opinion on non-reserved keywords ? >> Should they be included, excluded, separated ? non-reserved words are >> acceptable and do not get in the way of your queries. > > Re: "Non-reserved": > It seems that the definition of non-reserved varies a little depending > on the DB. > > The widest definition appears to be: any word which is recognised by > the parser. > > A more common definition appears to be: a word which has a special > meaning in a particular context but which may be used as an identifier > in other contexts. > > I have noticed that a non-reserved word can often be upgraded to be a > reserved word in a later DB version. > > Conclusion: It seems safer to include non-reserved words too. > However, if your code checker can identify both, brilliant. > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to web...@googlegroups.com. > To unsubscribe from this group, send email to > web2py+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
