> indeed associated with the connection, as I believe is usually the case on > most databases. Storm isn't playing any special role there.
I simply saw that the sqlite backend overrides raw_execute and appears to sends the BEGIN (and later the COMMIT) to the connection object, rather than the cursor object that the base would use, and thought that might make a difference. Apparently it doesn't, then. > There are many ways of doing it. SQLite just doesn't want to provide > you with interaction over a cursor while you commit the transaction. Ok, I see. I would very much appreciate you (or anyone) giving me a some pointers, if at all possible. The only alternative I think of is using a separate connection/Store object (which is no problem per se, so maybe that's indeed what I should do). Michael -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
