>> The problem is holding a cursor open, reading a result set, over the >> transaction boundaries. A working replacement would be: > > I am aware that this works, but we're talking about a potentially huge > number of rows here, loading them all in memory is not an option.
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. > Am I understanding correctly that the problem stems from the fact that > the Storm sqlite backend manages the transactions on a connection > level, rather than on the cursor level? I'm not entirely sure I understand what you mean here. Transactions are indeed associated with the connection, as I believe is usually the case on most databases. Storm isn't playing any special role there. -- Gustavo Niemeyer http://niemeyer.net -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
