[sqlalchemy] Re: SQLAlchemy 0.5.5 MySQL Issue

2009-11-29 Thread gizli
Thank you. That was exactly the problem. MyISAM engine was selected as default, changed to InnoDB and now the autoflush behavior is as expected. On Nov 28, 4:36 am, Alexandre Conrad alexandre.con...@gmail.com wrote: You may be using MyISAM storage engine which doesn't support transactions and

Re: [sqlalchemy] Re: SQLAlchemy 0.5.5 MySQL Issue

2009-11-28 Thread Alexandre Conrad
You may be using MyISAM storage engine which doesn't support transactions and may make all flushes persistent. The other storage engine widely used is InnoDB which does support transactions. Find out in the MySQL docs how to figure out which storage engine you're using. Sent from my fantastic HTC

[sqlalchemy] Re: SQLAlchemy 0.5.5 MySQL Issue

2009-11-27 Thread gizli
I am not sure about the storage engine but here goes: mysql status -- mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 the mysql-python version is MySQL_python-1.2.3c1 On Nov 26, 11:47 pm, Alexandre Conrad alexandre.con...@gmail.com wrote: 2009/11/27