Re: [SQLObject] MySQL and transactions
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
|
From: Jaime W. <pro...@gm...> - 2007-10-22 14:16:49
|
It turned out to be user error... My tables weren't INNODB, which I ASSumed would automagically happen after specifying the INNODB paramaters in the MYSQL ini file. Anyway, the answer to my problems were found here -> http://www.sqlobject.org/FAQ.html#how-can-i-specify-the-mysql-engine-to-use-or-tweak-other-sql-engine-specific-features Thanks! jw On 10/22/07, Oleg Broytmann <ph...@ph...> wrote: > > On Mon, Oct 22, 2007 at 07:59:34AM -0500, Jaime Wyant wrote: > > trans = conn.transaction() > [skip] > > The console output is below. I expected to see a `BEGIN` or `START > > TRANSACTION` somewhere at the beginning of the output, but it is not > there. > > Is this a bug, or user error :) ? > > Neither. Opening a transaction is implemented via DB API driver > - usually using its .autocommit() method, and what way the method is > implemented is up to the driver; SQLObject doesn't know what the driver > does. > > Oleg. > -- > Oleg Broytmann http://phd.pp.ru/ ph...@ph... > Programmers don't die, they just GOSUB without RETURN. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > sqlobject-discuss mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > -- "Government does not solve problems; it subsidizes them." Ronald Reagan |