do a pack all, install the app, run pg_restore, don't run any code. set fake_migrate_all=True, hit appadmin, set fake_migrate_all=False. voilà.
On Monday, February 8, 2016 at 7:11:06 PM UTC+1, Alex Glaros wrote: > > no, I did not compile. > > Postgres changes created by DAL work correctly on site #1 local machine. > They only do not work on site #2 when I copy the app from site #1. > > Could the problem be how I transfer the development to site #2? > > On site #1 I do a "pack all" in web2py, and a "pg_dump" on Postgres. > > Then at site #2, I do an "Upload and install packed application" on web2py > and a "pg_restore" on Postgres. At this point, I receive "table already > exists" errors, so I delete all databases in web2py database folder, drop > and re-create Postgres database from within Postgres, and re-run > pg_restore. Now the app on site #2 looks and works identical to site > #1...until I try modifying the model. Then I get the behaviour described > above where DAL changes never get implemented either on the Postgres side > or the web2py side. sql.log shows the changes implemented then inexplicably > deleted. The model is stuck in time. > > Did I copy from site #1 to #2 incorrectly? > > -- 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.
