[sqlalchemy] Sessions and threads, find in one thread, use in another

2007-12-13 Thread Allen Bierbaum
In my current application I am running a rather expensive query in a background thread, but then I need to use the results in the foreground thread. The object I find has a great deal of lazy evaluated properties that link it to several other mapped objects. As it stands now, the application is

[sqlalchemy] Re: Sessions and threads, find in one thread, use in another

2007-12-13 Thread Michael Bayer
On Dec 13, 2007, at 9:55 AM, Allen Bierbaum wrote: In my current application I am running a rather expensive query in a background thread, but then I need to use the results in the foreground thread. The object I find has a great deal of lazy evaluated properties that link it to several

[sqlalchemy] Fwd: [elixir] warnings on exit

2007-12-13 Thread Gaetan de Menten
Since this is not specific to Elixir and I don't know what could be the problem, I'm forwarding this to the SQLAlchemy list. You can watch that list for the answer (which will hopefully be given) or wait until I forward that answer to the Elixir list. -- Forwarded message --

[sqlalchemy] Double joined polymorphic inheritance ?

2007-12-13 Thread Alexandre Conrad
Hi, I'd like to know if it's possible to have multiple level of inheritance. Please find attached a test case where I'd like to have Site to inherit from Company and also be the base table for SiteClient and SiteSupplier. I guess I'd need a mix of the following syntax (from the test):

[sqlalchemy] Re: Sessions and threads, find in one thread, use in another

2007-12-13 Thread Allen Bierbaum
On Dec 13, 2007 10:47 AM, Michael Bayer [EMAIL PROTECTED] wrote: On Dec 13, 2007, at 9:55 AM, Allen Bierbaum wrote: In my current application I am running a rather expensive query in a background thread, but then I need to use the results in the foreground thread. The object I find

[sqlalchemy] Fetchall() in 0.4x

2007-12-13 Thread Rick Morrison
Just noticed that ResultProxy.fetchall() is a bit broken in 0.4x (I think it's for queries that do not populate the DBAPI cursor.description). In my case, it's executing a stored procedure that returns data: S.execute('exec schema.storedproc 1234').fetchall() Traceback (most recent call last):

[sqlalchemy] Re: Fetchall() in 0.4x

2007-12-13 Thread Michael Bayer
On Dec 13, 2007, at 11:51 PM, Rick Morrison wrote: Just noticed that ResultProxy.fetchall() is a bit broken in 0.4x (I think it's for queries that do not populate the DBAPI cursor.description). In my case, it's executing a stored procedure that returns data: S.execute('exec