Hi, I have a service that sends transactions to many different mysql nodes
using sqlalchemy, one basic requirement for this service is to always have
the same state in all the nodes, thus if one update in one node fails I
have to rollback the transaction in the nodes that the update had been
Wow thank you that was it! I had some newer tables created in MyISAM and
those table got to be always updated in transactions with other tables.
On Wednesday, July 17, 2013 4:57:02 PM UTC+2, Michael Bayer wrote:
On Jul 17, 2013, at 10:32 AM, Antoni Silvestre Padrós
antoni.s...@gmail.com
On Jul 17, 2013, at 10:32 AM, Antoni Silvestre Padrós
antoni.silves...@gmail.com wrote:
Hi, I have a service that sends transactions to many different mysql nodes
using sqlalchemy, one basic requirement for this service is to always have
the same state in all the nodes, thus if one update
Hi Michael,
Thanks for your help. Using 0.8.3 and the type variant passes our tests.
Do you have any (even rough) estimate as to when 0.8.3 will be released to
PyPI?
Thanks,
Basil
On Friday, 12 July 2013 18:56:14 UTC-7, Michael Bayer wrote:
Right, DateTime + with_variant() +
the nested transaction / savepoint syntax in sqlalchemy appears to be:
session = SessionFactory()
session.begin() # main tx
session.begin_nested() # outer tx
session.begin_nested() # inner tx
session.rollback() # innter tx
session.commit() #
On Jul 17, 2013, at 6:42 PM, Jonathan Vanasco jvana...@gmail.com wrote:
the nested transaction / savepoint syntax in sqlalchemy appears to be:
session = SessionFactory()
session.begin() # main tx
session.begin_nested() # outer tx
session.begin_nested() # inner
On Wednesday, July 17, 2013 7:02:10 PM UTC-4, Michael Bayer wrote:
because you can transfer control to some other part of the program that
doesn't know what kind of transaction has started; it only knows it needs
to call commit() or can rollback() if something goes wrong.
It's a simple
On Jul 17, 2013, at 10:10 PM, Jonathan Vanasco jvana...@gmail.com wrote:
On Wednesday, July 17, 2013 7:02:10 PM UTC-4, Michael Bayer wrote:
because you can transfer control to some other part of the program that
doesn't know what kind of transaction has started; it only knows it needs to
well we try to get releases out every 4-6 weeks but sometimes it takes longer.
though this issue was a surprise and does lean things towards releasing
sooner.
On Jul 17, 2013, at 12:38 PM, Basil Veerman bveer...@uvic.ca wrote:
Hi Michael,
Thanks for your help. Using 0.8.3 and the
How can I make all datetime columns to use my UTCDateTime type by default?
from sqlalchemy import types
from pytz import utc
Base = declarative_base()
class UTCDateTime(types.TypeDecorator):
impl = types.DateTime
def process_bind_param(self, value, engine):
if value is not
10 matches
Mail list logo
