I still insist, unless convinced otherwise, that the migrate switch at the moment logically wrong if it takes a string for the table files, there should be a separate variable that controls the creation of .table files because one would not want to migrate a database( migrate = False) but just modify an existing database based on a modified model Specifics:
1. I use PostgreSQQL 2. The initial upload was done by packing the BETA/ local version of the appliance to the LIVE server After changes, only the BETA server appliance gets deleted and the new version from my local machine gets uploaded to it using upload app. I cannot use this procedure for the LIVE server due to the problems above so i just overwrote the model file of the LIVE server appliance expecting the web2py to ALTER the tables, but this does not happen because .table files exist. All 3 appliances are identical, if I make changes to the model file in local version of the appliance, the changes are made, so I should expect that just uploading the modified model file to the appliance on the LIVE server should ALTER the tables as it did on my local machine. Nothing else has changed except the a few lines in the model file. I still insist, unless convinced otherwise, that the migrate switch at the moment logically wrong if it takes a string for the table files, there should be a separate variable that controls the creation of .table files because one would not want to migrate a database( migrate = False) but just modify an existing database based on a modified model --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
