@Jonathan Vanasco:
i have no input on the issues michael identified.
but i'm curious about a sqlalchemy event somehow not firing. which
transaction event were you using? after_begin or after_transaction_create
?
I used the after_begin event to set the search_path, but moved it into the
On Sep 12, 2014, at 6:45 AM, Matthijs Blaas thijs.bl...@gmail.com wrote:
Ok, i found the issue!
When I tried to use pg8000 to connect to postgres i got an error: cannot
insert multiple commands into a prepared statement.
Apparently multiple queries is fine with psycopg2, but not using
i have no input on the issues michael identified.
but i'm curious about a sqlalchemy event somehow not firing. which
transaction event were you using? after_begin or after_transaction_create
?
--
You received this message because you are subscribed to the Google Groups
sqlalchemy
set the search path within the connection pool using the “connect” event;
all connections used by the pool will then have this search path setting
the moment they connect. Don’t ever put multiple SQL expressions in a DBAPI
execute (for this very reason - driver changes, hilarity ensues. We are
On Sep 12, 2014, at 12:26 PM, Matthijs Blaas thijs.bl...@gmail.com wrote:
set the search path within the connection pool using the connect event;
all connections used by the pool will then have this search path setting
the moment they connect. Don't ever put multiple SQL expressions in a
I'm expiriencing some strange bugs which seem to be caused by connections
used by Sqlalchemy, which i can't pin down exactly.. i was hoping someone
has a clue whats going on here.
We're working on a Pyramid (version 1.5b1) webapplication and use
Sqlalchemy (version 0.9.6) for all our database
