|
From: SourceForge.net <no...@so...> - 2006-03-21 09:47:44
|
Bugs item #1455251, was opened at 2006-03-21 12:47 Message generated for change (Tracker Item Submitted) made by Item Submitter 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: Open Resolution: None Priority: 5 Submitted By: Oleg Broytmann (phd) Assigned to: Nobody/Anonymous (nobody) 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1455251&group_id=74338 |
