The problem is that ContentObserver.onChange() doesn't tell you what changed. So how do you figure it out? Well, as far as I can tell you have to keep your own copy of everything you might care about in the database, and then when you get onChange() you read everything from the ContentProvider and then compare it to your local copy, looking for changes. That is, you have to rescan the database with every change, not just between instantiations. But if I'm wrong, please tell me!
Since you (DB) are storing a local copy anyway, this might be feasible, but for most purposes this is just too onerous to be useful. I really hope they fix this API to indicate what has changed, because ContentObserver is a nice idea - it allows different frontend and backend applications to share a common data pool. --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
