Are you trying to keep the production database and just run migrations on it, or just create a whole new production database from scratch to match the new code? If the former, don't touch the /databases folder on production -- just update the code and leave migrations on, and the DAL will run the proper migrations to make the production database match the new models.
Anthony On Wednesday, October 11, 2017 at 7:49:07 AM UTC-4, Yebach wrote: > > Hello > > So based on all the material I have read about migration etc some of the > updates are not working. I will explain what I am doing and please correct > me where my steps are wrong > > I going from develop to production version and the key is to keep the > database with its current data. > > > 1. I backup my production database > 2. I created new directory with my develop web2py files - DAL is > different in a way i have some new tables and some new fields compare to > my > production version of the database > 3. copied all the files and folders to create a new app > 4. deleted ALL files in App/database folder > 5. restored database on Postgres under new name > 6. Set migrate = True and fake_migrate = True in 0.py file > 7. run web2py with web2py.exe -i 192.168.100.47 -p 8000 -a 12345 -K > WoShiTest -X > > Now the tables are not updated and also new tables are not added. > > What am I doing wrong? > > I am using the version of web2py downloaded on 11.10.2017 > > Thank you > > Best regards > -- 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.
