Rakoun wrote: > Thanks Mark but what about the sentence "Inserts a row into a table at > the given URL. If the content provider supports transactions the > insertion will be atomic." in the ContentResolver insert method > documentation?
That says a *single* insert() call *may* be atomic. If I understood you correctly, you want *multiple* insert()/update()/delete() calls to be atomic. Not only might the ContentProvider not be atomic in general (e.g., not storing in SQLite), but there is no way to set up a transaction across multiple API calls to the ContentProvider. If you want such transactions, don't use a ContentProvider -- access SQLite directly. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Looking for Android opportunties? http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
