Hi Massimo, I would like to suggest that the switch that toggles migration should be disambigous. My reason? I tried to migrate a live PostgreSQL database some days ago and I ran into problems that I could only solve manually.
Right now, we have this "toggle", migrate, which can be either a boolean True or False. This notifies the application if it should create tables or not. As simple thing actually. The ambiguity comes from the added feature of being able to pass this toggle switch a string which denotes the name of a database schema file which web2py creates depending on the situation. This is the prefferred web2py method. I have 3 "codebases" for a site, I use the word codebase for lack of a better term since I use Subversiion for versioning and its not the same as having a local, beta and live setup of a site. I made changes to the local version of the site on my workstation and uploaded to my "BETA" server, then I got a multitude of errors about tables that could not be migrated because they exist already and so on, deleting the files in the databses folder is not an option because you get tickets based on the fact that databases already, toggling the migrate to False does not re-create the database files for you either since they exist, and so on...it all gets recursive in some cases Would it not be better to have a varibare that notifies web2py to generate the databse files or not and a separate one that toggles migration? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
