[sqlalchemy] Re: Query is checking for transaction status - Harish - com.googlegroups.sqlalchemy

4 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Query is checking fo...

From	Sent On	Attachments
Harish	22 Jul 2008 14:33
Michael Bayer	22 Jul 2008 14:38
Harish	22 Jul 2008 15:48
Harish K Vishwanath	23 Jul 2008 10:11

Subject:	[sqlalchemy] Re: Query is checking for transaction status
From:	Harish (hari...@gmail.com)
Date:	07/22/2008 03:48:25 PM
List:	com.googlegroups.sqlalchemy

Thanks for looking into this.

I am using Elixir coupled with SqlAlchemy. Elixir's global contextual session is set to None (in using_options). Each thread gets its own Database interface object (dbo).

Each dbo has a sqlalchemy session, url and engine object. All the threads talk to the same Sqlite database. When an engine is constructed, will there be a separate connection created for that engine?

But I do : elixir.metadata.bind = self.engine elixir.metadata.bind.echo = echo in the constructor call of dbo object.

Therefore the global elixir's metadata object is bound to the last created engine which is created in the dbo's constructor object. Is this the problem?

All flush operations occur through a single method sqlCommit() which handles and logs the exceptions. I did not get any flush errors before the exception mentioned earlier occurred.

Thanks for your inputs!

On Jul 22, 2:38 pm, Michael Bayer <zzz...@gmail.com> wrote:

On Jul 22, 5:33 pm, Harish <hari...@gmail.com> wrote:

The session is transactional with autoflush=False. Why is a query trying to find out the status of session? Is there anything that could have been done wrong?

Thanks in advance for the help!

that error is usually when flush() raises an error yet further operations are continued upon the underlying connection. Since the error occurs randomly, this very strongly suggests unsynchronized access by multiple threads to either a single Session or a single Connection underlying it.