I had mistaken it for a SQLA flaw, but, from pdb, it appears the
behavior I'm observing is being caused by zope.sqlalchemy.
Thanks for your input.
On Dec 16, 7:19 pm, Michael Bayer mike...@zzzcomputing.com wrote:
That doesn't sound right. Session.commit() issues the commit regardless of
Doesn't seem like anyone has any thoughts here. Its certainly not something
I've tried, but the general area of study here is multi-master replication:
http://en.wikipedia.org/wiki/Multi-master_replication . The various ways of
dealing with whos dirty and whatnot fall under that realm of
Hi there,
If i define a new table unrelated (without foreign keys) to the tables
that already exist i see that this new table is created automatically
when i create the session.
But if i create a new column to a table that already exist this new
one isn't created when i start the application. Is
On Dec 17, 1:21 pm, Michael Bayer mike...@zzzcomputing.com wrote:
Doesn't seem like anyone has any thoughts here. Its certainly not something
I've tried, but the general area of study here is multi-master replication:
http://en.wikipedia.org/wiki/Multi-master_replication. The various
(Sorry, I mis-clicked before.)
I've used MySQL replication for sharing data from multiple databases.
You can organize the servers in a loop and configure them to pass
along the changes replicated by other servers. Of course if any
server fails, the loop is broken until that server is running
