Id say you have to monkeypatch Connection._execute_raw() with a
wrapping method for now (or dialect.do_execute()/do_execute_many
()).I have observed that "execute()" is not the only place you
might get an exception. sometimes you get it when calling cursor()
(we do catch those and inv
> throw consistent errors at consistent points of execution. if you
> think your database was stopped and is now re-started, you can call
> invalidate() on an individual connection and then close() it for it
> to be replaced in the pool, or more likely you can call dispose() on
> your engine and
On Mar 15, 2007, at 12:19 PM, vinjvinj wrote:
> cases above. Ideally you would want the database layer to recreate the
> connection and then try to execute the statement again.
whys that ? what if you just have the wrong connection string, or
the database is stopped ? do you expect the data
