All I am saying is that if you need to do a migration, first take web2py down, then run it on localhost only, they do the migration and debug eventual errors. Do not change your model while your app is being exposed to users.
There is nothing wrong in principle but there is always the possibility of a typo or other minor error and you do not want to give lots of tickets to your users. Said this. I always change my models in production. We did it twice with the PyCon registration site. Massimo On Mar 1, 9:39 am, annet <[email protected]> wrote: > Alexandre and Massimo, > > Thanks for your replies. > > > Anyway, for various reason I would not suggest doing migrations while > > in production because they may lock the database for some time. > > I am reading a bachelor in computer science so I am not a complete > novice when it comes to analysis and design, however, no matter how > well I designed my model, one day I will have to do migrations because > of changes in the domain (relevant world). How do I proceed in that > case? > > What about the 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 -~----------~----~----~----~------~----~------~--~---
