If you don't change this line both in production and in test auth.define_tables(migrate=False, username=True, signature=False)
the error that you are getting will NEVER pop up. If migrate=False, web2py doesn't attempt to create the auth tables, so the error "table_auth_user already exists" DOESN'T pop up. are you sure that what you're reporting is exatcly what's happening ? On Wednesday, April 30, 2014 8:13:43 AM UTC+2, Annet wrote: > > Hi Richard, > > Thanks for you reply. > > Personally, because I didn't have the control I want on migration, and I >> don't want to lost data. I don't do that. I update the prod database >> manually... >> > > > I've considered this too but wasn't sure about how to proceed. What you do > is alter your database in the admin tool on the database (pgAdmin3 or > phpPgAdmin in my case), > in the connection string set migrate=False, fake_migrate=True and in the > table definition set migrate = 'table_name.table'. > > Is that correct. > > Regards, > > Annet > -- 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.
