I have thought about setting up a shared postgres. However the issue still remains that if the .table files are altered during two branches, when merging how do you pick which .table file to accept?
And you can't get rid of .table files because then you would not be able to connect to the postgres database. Would it work if we did not version the .table files, and set fake_migrate = True on all of the define_table statements? Then would we be able to still have automatic migrations? -Thadeus On Tue, Feb 9, 2010 at 4:38 AM, tiago almeida <tiago.b.alme...@gmail.com> wrote: > hy not setup a shared db server on the network? It works, just needs some > coordination when making changes to the model. Does it have to be sql -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
