On Fri, Oct 12, 2012 at 3:53 PM, Simon Slavin <slav...@bigfraud.org> wrote: > That's an interesting idea. I have a question. Suppose your program > received the 'success' result for a transaction and carried on to do other > transactions. Later you test to see whether the transaction is durable and > find that it isn't. What would be a useful thing to do at that point ?
It depends. For most such applications I'd say this is just not appropriate. But you might have an application where this is fine, provided you have a way to reflect the D/not-D state of the initial transaction in the dependent ones. What I had in mind was something more like a booking system: let the user know that the transaction completed by updating the page so as to make the form go away, but leave an indicator (e.g., animated ellipsis) to indicate that the transaction is not quite completed. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
