Most projects on svn.zope.org have the policy to perform new work on
the trunk, cutting maintenance branches from it when appropriate.
RelStorage appears to forge ahead on its 1.1 branch, allowing the
trunk to go stale.
What's the policy here? If I wanted to create a branch to work on
This is not a problem of the ZODB or relstorage, but specific to how
MySQL handles a) replication and b) temporary tables.
MySQL employs a log-based replication mechanism. This means the
replication slave replays the commands performed on the master to
keep its copy of the database in
Stefan H. Holek wrote:
Most projects on svn.zope.org have the policy to perform new work on
the trunk, cutting maintenance branches from it when appropriate.
RelStorage appears to forge ahead on its 1.1 branch, allowing the
trunk to go stale.
What's the policy here? If I wanted to create
Stefan H. Holek wrote:
In MySQL, temporary tables live in RAM. So when a slave goes down,
its copy of the table vanishes. When the slave comes back up the log
may still contain commands using the temporary table however, causing
execution to barf (and replication to stop). To fix this
