On Fri, Oct 12, 2012 at 5:14 PM, Simon Slavin <slav...@bigfraud.org> wrote: > I think I understand what you're asking for, but I see no point in being > informed about D, because I can't see anything useful a program can do if the > transaction gets marked 'complete' but D doesn't succeed. Either you see D > as being part of a transaction, or you don't.
A server application might not know which the client wants. And sure, the client could tell it. But I think that to be general and thus support arbitrary layering, having an option to pass this indication through is best. > By all means, use a PRAGMA to day whether you do need D or not. SQLite > already has a dozen ways to do this (though it is very puzzling to try to > work out what combination of PRAGMAs to use under your conditions). But > report D (or ignore D) as part of the result of 'COMMIT'. Don't make an > extra status for "committed but not durable'. We disagree then. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
