> 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. 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? Michael -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
