The checking is off by default, you have to explicitly enable it. Therefore unless he is using it, it is not causing a problem. And the error message looks nothing like the one that the check emits anyways :)
It would help if we had a stack-trace to see where the error is being triggered. -Thadeus On Sat, Mar 6, 2010 at 5:07 PM, villas <villa...@gmail.com> wrote: > It's probably due to SQL Reserved Keywords: web2py.com/book/default/ > section/6/2 > > Password didn't previously seem to cause a problem in MySql itself, > but it should still be avoided so that your app is more transportable > across DBs. I am not sure how to turn off the checking, but I imagine > it will be easy enough. > > As this problem with 'password' does arise regularly because of the > default Auth_Users table, I wonder whether Massimo might find a way to > default this to 'passwd' for future apps? > > -- > 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.
