Hello Michael,
Thank you for your replies. I've just tried to create a testcase but
proven to myself that it does raise an exception. I'll go back and
double check where I might be catching and passing on the exception.
Daniel
On Apr 29, 3:19 pm, Michael Bayer mike...@zzzcomputing.com wrote:
Daniel wrote:
I've learned a bit more. Apparently the sqlite database occasionally
gets locked by another process and that lock lasts longer than the
five second default timeout. SQL Alchemy quietly issues a ROLLBACK,
but doesn't say anything more about it. The result is that the
session
how is it that you know this is due to the SQLite timeout ? did you
create a test case ? creating a fully reproducible test case would be
the next step.
On Apr 29, 2009, at 5:15 PM, Daniel wrote:
I'm not catching it or re-raising it. Where else could I look to
solve this.
On Apr
squelching typically means one of two things.
either you're doing this:
try:
# do stuff with session
except:
print error !
# .. keep going
or, you are allowing concurrent access to a single session with
multiple threads, one of your threads is throwing an exception
(usually
