On 5/15/2012 1:55 PM, Charles Samuels wrote:
The question here is: where can I put that "more data" so that it won't be part of checkpoint 1, but is still accessable by sqlite select statements? (Accept that otherdb allows asychronous commits such that I can add more data to it that doesn't wind up on disk).
Well, SQLite doesn't. Basically, you want SQLite to maintain multiple not-yet-committed versions of the same record. I don't believe there's any way to get it to do that automatically - you'll have to come up with an explicit versioning scheme (like your idea of creating a temporary shadow database).
* If sqlite had a "commit transaction to savepoint X", then sqlite commits to the oxide everything up to a specific savepoint, keeping the savepoints after those committed still as active and uncommitted savepoints. The only disadvantage I can think of to this is that sqlite has no such feature.
"Oh yes, I thought of something... but unfortunately, it rather involved being on the other side of this airtight hatchway." -- The Hitchhiker's Guide to the Galaxy.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
