Michael,
On Mar 25, 3:00 pm, Michael Bayer mike...@zzzcomputing.com wrote:
SQLAlchemy also doesn't issue BEGIN. You might want to look at setting
autocommit to false on your MySQLdb connection, since that's the layer that
would be sending out BEGIN.
I looked into this. BTW, I use
keith cascio wrote:
Every COMMIT is followed by a ROLLBACK, which appears wasteful. Which
software do I blame for that, SQLAlchemy or the MySQLdb DBAPI
connector?
It's not wasteful at all in the usual case unless one wants to have
leftover row/table locks and transactional state sitting idle
Michael,
I apologize if I came off at all rude. I noticed how helpful you are
and I value your advice. Thank you for your patience.
On Mar 26, 1:21 pm, Michael Bayer mike...@zzzcomputing.com wrote:
It's not wasteful at all in the usual case unless one wants to have leftover
row/table locks
On Mar 26, 2010, at 7:36 PM, keith cascio wrote:
Here is a ping from the real production client against the real
production server:
$ /usr/sbin/ping -s a.bbb..d.com
.
.
a.bbb..d.com PING Statistics
17 packets transmitted, 17 packets received, 0% packet
Michael
On Mar 25, 12:33 pm, Michael Bayer mike...@zzzcomputing.com wrote:
nothing ever refreshes automatically. only things that have been
expired, or were never loaded in the first place, are loaded when requested.
Good to know.
to reduce expirations,
2010-03-25 13:19:02,049 INFO sqlalchemy.engine.base.Engine.0x...f054 BEGIN
2010-03-25 13:19:02,049 INFO sqlalchemy.engine.base.Engine.0x...f054 UPDATE
xxx SET yyy=now() WHERE xxx.z = %s AND xxx.a = %s
2010-03-25 13:19:02,049 INFO sqlalchemy.engine.base.Engine.0x...f054 [193302,
Michael
On Mar 25, 1:27 pm, keith cascio keithautoma...@gmail.com wrote:
However, now that I did, things are more complicated, and SQLAlchemy 0.5
complains.
2010-03-25 13:19:02,049 INFO sqlalchemy.engine.base.Engine.0x...f054 BEGIN
2010-03-25 13:19:02,049 INFO
Michael
On Mar 25, 1:50 pm, Michael Bayer mike...@zzzcomputing.com wrote:
SQLA uses the DBAPI in its default mode of autocommit=False and is always
going to issue flushes followed by a COMMIT or ROLLBACK. There's also a
ROLLBACK which occurs automatically via the connection pool and you
keith cascio wrote:
Michael
On Mar 25, 1:50 pm, Michael Bayer mike...@zzzcomputing.com wrote:
SQLA uses the DBAPI in its default mode of autocommit=False and is
always going to issue flushes followed by a COMMIT or ROLLBACK.
There's also a ROLLBACK which occurs automatically via the
keith cascio wrote:
Michael
On Mar 25, 1:50 pm, Michael Bayer mike...@zzzcomputing.com wrote:
SQLA uses the DBAPI in its default mode of autocommit=False and is
always going to issue flushes followed by a COMMIT or ROLLBACK.
There's also a ROLLBACK which occurs automatically via the
10 matches
Mail list logo
