I think you might want to try: 1. copy all of the files in "databases" somewhere safe 2. delete all the files in "databases" 3. in the DB connection string, include (..., migrate=True, fake_migrate_all=True) 4. Access /appadmin to trigger a migration 5. Revert DB connection string to (..., migrate_enable=False, fake_migrate_all=False)
I believe this is safe but if you can try it out on a backup or test db, might be prudent. On Wednesday, November 14, 2012 7:24:39 PM UTC-8, Richard Penman wrote: > > Having trouble migrating with postgres. > > With fake_migrate=True the the .table files are created. > > If migrate=True then error: auth_user already exists. > > Tried all combinations of these and deleting and removing .table files, > but no joy. > > Is web2py meant to support modify the tables with postgres? If so which > combination of options would you recommend? > With sqlite this works fine. > --
