I'm not catching it or re-raising it. Where else could I look to solve this.
On Apr 29, 11:57 am, "Michael Bayer" <[email protected]> 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 is no longer active and eventually produces the error I > > mentioned above. Here are the log messages showing the insert failing > > after the five second default timeout. > > > 2009-04-28 15:10:48,118 INFO sqlalchemy.engine.base.Engine.0x...ae70 > > INSERT INTO table ("id", "value") VALUES (?, ?) > > 2009-04-28 15:10:48,118 INFO sqlalchemy.engine.base.Engine.0x...ae70 > > [1, 'my value'] > > 2009-04-28 15:10:53,148 INFO sqlalchemy.engine.base.Engine.0x...ae70 > > ROLLBACK > > > Is there some way to configure SQL Alchemy to raise an exception when > > it issues the rollback, or when it finds the database locked? > > SQLAlchemy definitely raises an exception if the DBAPI sends one. a > ROLLBACK does not occur if there was no exception thrown. check if > you're catching it and not re-raising. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
