A couple of month ago I raised the following question: Every now and then simple changes to my model raise errors I do not understand. My PostgreSQL database contains example records for development purposes, so it is no big deal to drop and re-create some tables. But what if these errors occur after deployment on a production server.
After initial deployment, when I continue developing my application, the database in my development environment will start to differ from the one on the production server. When I redeploy my application on the production server, the files that make up the model match my development database, but not my production database. How does web2py deal with these differences? Since the question wasn't answered I post it again, at the time of posting is was just me wondering about web2py's behaviour, now that I am nearing the point of deployment on a production server the answer to this question has become much more important. I wonder whether it is a good idea to put the database model in the init application and copy and paste it to the applications that make use of the model and set migrate to False? Best regards, Annet --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
