|
From: SourceForge.net <no...@so...> - 2006-03-27 14:58:38
|
Bugs item #1455251, was opened at 2006-03-21 12:47 Message generated for change (Settings changed) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1455251&group_id=74338 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted >Resolution: Wont Fix Priority: 5 Submitted By: Oleg Broytmann (phd) >Assigned to: Oleg Broytmann (phd) Summary: dbConnection.query() opens another connection Initial Comment: DBConnection often uses self.query() to run additional queries. That's acceptable for DDL queries (CREATE/DROP) but is very bad for DML queries (SELECT/INSERT/UPDATE/DELETE) because the new query is executed in a different connection, outside of the current transaction. Even worse, for row.destroySelf() SQLite often fails with the error "Database is locked". DBConnection mustn't use self.query(); the query must be run via the current low-level (raw) connection. ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-03-27 18:58 Message: Logged In: YES user_id=4799 It seems it's me overgeneralizing a problem with .destroySelf(). See http://sourceforge.net/mailarchive/forum.php?thread_id=10043224&forum_id=30269 for a discussion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1455251&group_id=74338 |
