[SQLObject] SQLObject 0.7.9b3, 0.8.6b3 and 0.9.2b3

2007-10-22 Thread Oleg Broytmann
http://cheeseshop.python.org/pypi/SQLObject/0.7.9b3 http://cheeseshop.python.org/pypi/SQLObject/0.8.6b3 http://cheeseshop.python.org/pypi/SQLObject/0.9.2b3 * Changed the implementation type in BoolCol under MySQL from TINYINT to BOOL (which is a synonym for TINYINT(1)). Oleg. -- Oleg

Re: [SQLObject] BoolCol and the backend datatypes

2007-10-22 Thread Markus Gritsch
On 10/22/07, Oleg Broytmann [EMAIL PROTECTED] wrote: *) TINYINT is not part of ANSI SQL and should IMO therefore not be used in the SQLite backend. SQLAlchemy uses BOOLEAN. Changed in the trunk along with fromDatabase in the revs 3112-3113. They are released as versions 0.7.9b3,

[SQLObject] MySQL and transactions

2007-10-22 Thread Jaime Wyant
Hi all. Can anyone tell me why the code below commits rows to the table? I've read the documentation and I'm not quite sure why it is happening. # BEGIN CODE SNIPPET from sqlobject import * conn = connectionForURI('mysql://user:[EMAIL PROTECTED]/test?debug=1') class TestTable(SQLObject):

Re: [SQLObject] MySQL and transactions

2007-10-22 Thread Jaime Wyant
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 -

Re: [SQLObject] MySQL and transactions

2007-10-22 Thread Dan Pascu
On Monday 22 October 2007, Jaime Wyant wrote: Hi all. Can anyone tell me why the code below commits rows to the table? I've read the documentation and I'm not quite sure why it is happening. # BEGIN CODE SNIPPET from sqlobject import * conn = connectionForURI('mysql://user:[EMAIL