http://bugs.gpodder.org/show_bug.cgi?id=180
Justin Forest <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #3 from Justin Forest <[EMAIL PROTECTED]> 2008-09-16 20:08:47 ---
db.commit() can safely be delayed. There's only one SQLite "connection",
shared by all threads, so if there's an open transaction, all threads are in
it.
I'm not sure if these commits are actually doing anything, because the
transaction isn't open anywhere and it's unclear whether SQLite is in
autocommit mode by default.
It could be a good idea to rename db.commit() as db.flush(), which would commit
the current transaction and start the new one immediately. They say that
SQLite is so much faster inside a transaction, but I've yet to test this.
--
Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs
