I'm having a problem with a specific nested transaction in my project. It calls one method twice, which consists of a single database insert and a nested call to another method, which has a possibility of multiple deletes followed by multiple inserts, or no transactions at all, and then a single update. This method, when called elsewhere in my project, works fine 100% of the time I've used it. It reaches the end (and if successful) sets the transaction as successful and ends. After it calls this method twice, it calls another one, which consists of one insert. So far, up to this point, everything works fine; all of the data returned from these methods exists and is valid. But once I set the parent transaction as successful and end the transaction, all of the data which previously existed is gone from the database, like it was never committed.
So what I'm running in the situations I'm testing is a transaction which consists of 2 child-levels of nesting, and a minimum of 5 inserts/updates/deletes. It doesn't seem like sqlite should be crapping out on me with that little amount of data. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
