On 18 Aug 2013, at 10:48 AM, at <[email protected]> wrote: > Thank you for detailed explaination. > > Sorry I couldn't understand that how can we live with a blank databases > folder? > > Suppose server1 is active and it has filled databases folder, and server2 is > passive with empty databases folder. Both are pointing to same database which > is on server3. My understanding is when server1 will become passive and > server2 active, application (running on server2) will crash because it will > try to create tables in the database and these tables are already exist? > Please correct me.
The table files are needed only for migration. By "active", Niphlod means the server responsible for doing migrations; the "passive" server never performs migrations, so it never needs table files. Notice that, apart from migrations, the servers "know" about the database schema from the define_table calls, not from the table files. > > Thanks & Regards > > On Sunday, 18 August 2013 14:35:53 UTC+5, Niphlod wrote: > 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.
