@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 connect event like Michael suggested. @Michael Bayer: > SQLAlchemy never does that but I don’t know what you’d be doing in your code, it’s certainly a pattern that is supported and possible, just wouldn’t happen implicitly. Ok good to know! Im pretty sure there isnt anything done with connections in our code explicitly, so it probably had something todo with either the session not being cleaned up in the right event hook or the multiple commands in one query.. With the adjustments made i haven't been able to reproduce any of the errors so far, so thanks for the help!
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
