A couple of things: "name" is not a "reserved keyword" (see URL Fran referenced) - which means "name" is OK as a table or column name. And since "name" doesn't appear reserved in any of the SQL standards listed, I think this should be ok in other backends also...
'user' however _IS_ a reserved keyword in all the SQL standards listed in that link. You can modify it to be 'user_' which will always be safe, or some other thing - 'my_user', etc. As Fran pointed out, anything in that list which is reserved in any version of SQL is just not a fair table or column name for any database (not just Postgres) Regards, Yarko On Mon, Dec 29, 2008 at 3:10 PM, Fran <francisb...@googlemail.com> wrote: > > On Dec 29, 9:03 pm, Alex <shes...@gmail.com> wrote: > > So only solution to rename tables and fields everywhere ? > > AFAIK, yes...sorry... > > F > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@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 -~----------~----~----~----~------~----~------~--~---
