I suspect this is a sqlite bug.
1) make sure you are running the newest version of sqlite with pysqlite
compiled against it
2) if that doesn't fix it, try and isolate it into a sqlalchemy only or
maybe even sqlite only test case.
Laurence
Malthe Borch wrote:
With an in-memory engine, I seem to lose track of the tables after the
first response.
Turn of events:
1. Request comes in
2. Create some tables
3. Add content and commit transaction
4. Query content
5. Return response
Now...
6. New request comes in
7. Query content
(OperationalError) no such table: mytable ...
With a disk-based database, no errors occur. The point of my little
story line was to illustrate that this does not have anything to do with
transactions being committed.
\malthe
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
