> > > If connection string is same, can we generate .table files in one server > and then use them in other server? > > of course
> Actually we've two web2py servers (active & pasive) pointing to single > database server and we need to sync the database folder on both servers > when db model is modified. > > well, you can keep it "clean" on the master and then synchronize the folder to the passive. BTW, if there are multiple filenames for the same table you don't need to worry, web2py will only pickup the one needed. You're fine as long as the same files on the "working" version are the same in the other one. Also, .table files are just needed for actual migrations, so remember to set migrate=False if you don't change any table definition. Once the migration has been done and you set migrate=False, you can totally live with an empty databases/ folder because .table files are not necessary. My point being: depending on your architecture, you may decide to have migration happening only on server1 (where you keep your databases/ folder "filled") and have server2 with migrate=False with no .table files whatsoever. -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
