Re: [SQLObject] Problems with transaction-objects' persistence

2006-02-06 Thread Oleg Broytmann
Hello! On Wed, Feb 01, 2006 at 12:06:43PM -0500, Justin Azoff wrote: > Sounds familiar... I have to use the attached patch in order for > transactions to work correctly. It was posted on the list but I'm not > sure if it was ever applied. > > Without it, autocommit gets stuck turned off, and n

Re: [SQLObject] Problems with transaction-objects' persistence

2006-02-01 Thread Franz Pletz
* Justin Azoff <[EMAIL PROTECTED]> [2006-02-01 12:06:43 -0500]: > > Sounds familiar... I have to use the attached patch in order for > transactions to work correctly. It was posted on the list but I'm not > sure if it was ever applied. > > Without it, autocommit gets stuck turned off, and new

Re: [SQLObject] Problems with transaction-objects' persistence

2006-02-01 Thread Oleg Broytmann
On Wed, Feb 01, 2006 at 12:06:43PM -0500, Justin Azoff wrote: > def _makeObsolete(self): > self._obsolete = True > +if self._dbConnection.autoCommit: > +self._dbConnection._setAutoCommit(self._connection, 1) > self._dbConnection.releaseConnection(self._con

Re: [SQLObject] Problems with transaction-objects' persistence

2006-02-01 Thread Justin Azoff
Franz Pletz wrote: Hello, I'm currently using sqlobject (current svn) in conjunction with cherrypy (also current svn) and postgresql 8.1 for a project where I experienced some problems while using transactions with quite a few concurrent users. Sounds familiar... I have to use the attached p

[SQLObject] Problems with transaction-objects' persistence

2006-01-31 Thread Franz Pletz
Hello, I'm currently using sqlobject (current svn) in conjunction with cherrypy (also current svn) and postgresql 8.1 for a project where I experienced some problems while using transactions with quite a few concurrent users. Basically, after committing a transaction it won't get cleared from mem