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 <[email protected]> wrote: > 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 Hero > > On Nov 28, 2009 7:27 AM, "gizli" <[email protected]> wrote: > > 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 <[email protected]> > wrote: > > > 2009/11/27 gizli <[email protected]>: > > > > With mysql however, the insert done by the query() actually does a > > > > commit.. i turned on ec... > > -- You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. To... -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
