Yeah, I mean this could only work automatically, if all databases were SQLite and SQLite supported cross database journaling. But, I guess SQLite is not that sophisticated.
On May 18, 6:34 pm, Kostya Vasilyev <[email protected]> wrote: > In general, probably not, especially since a ContentProvider is not > necessarily back by a database. And if it is, then which one? It's not > necessarily the same as the database used in doSomeOfMySqliteStuff. > > If the content provider is your own, you can have a "backdoor" method to > support this, or perhaps not even that, because you just know that the > database object is the same in both cases. > > There are also ways to send entire batches of operations to a content > providers, but I assume you know about those, and in any case they don't > expose the transaction used (or not). > > -- Kostya > > 18.05.2011 11:37, Zsolt Vasvari пишет: > > > > > > > My guess is no, but I figured I'd ask. Is there a way to involve a > > ContentProvider as part of a transaction? > > > In effect (psuedocode): > > > try > > { > > beginTransaction(); > > > doSomeOfMYSqliteStuff(); > > doSomeStuffWithAContentProvider(); > > > commitTransaction(); > > } > > finally > > { > > endTransactions(); > > } > > > And doSomeOfMYSqliteStuff() and doSomeStuffWithAContentProvider() be > > atomic? > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com- Hide quoted text - > > - Show quoted text - -- 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
