Hi All,
The attached package gives that smallest possible example of problems
I'm hitting with some SQLAlchemy declarative classes.
In short, I want to be able to do:
python -m pack.module and have if the __name__=='__main__' block spit
out the SQL to create the tables necessary for the
ive no idea what __main__.py is either ? where's the SQLAlchemy exceptions
here ? (keeping in mind i havent yet gone through all the steps to download a
file...untar it...figure out what you're trying to do...)
On Oct 3, 2011, at 6:11 AM, Chris Withers wrote:
Hi All,
The attached
On 03/10/2011 15:15, Michael Bayer wrote:
ive no idea what __main__.py is either ? where's the SQLAlchemy exceptions
here ? (keeping in mind i havent yet gone through all the steps to download a
file...untar it...figure out what you're trying to do...)
The attached .tgz simplifies the
On Mon, Oct 3, 2011 at 4:24 PM, Chris Withers ch...@simplistix.co.ukwrote:
On 03/10/2011 15:15, Michael Bayer wrote:
ive no idea what __main__.py is either ? where's the SQLAlchemy
exceptions here ? (keeping in mind i havent yet gone through all the steps
to download a file...untar
Good afternoon,
We're using SQLAlchemy 0.6.6 and cx_Oracle 5.0.1, and our DBAs have
raised a concern about the number of sessions being kept open (where a
session is an Oracle concept, and a connection is on the socket).
We'd like to be able to keep the connection persistent, but we'd like
to be
This is a problem that would need to be solved mostly on the cx_oracle side,
then using standard SQLAlchemy APIs to implement.
Some googling didn't turn up a definitive answer if a single OCI connection can
persist, while its underlying session is killed. I found
On Oct 3, 2011, at 2:20 PM, Michael Bayer wrote:
3. Use pool events to emit commands when connections are checked out or
checked in. If you need to emit some SQL or cx_oracle commands on the DBAPI
connection upon checkout or checkin, the Engine provides pool events which
accomplish
