The app we're writing has a huge amount of code in it that reproduces almost exactly the functionality behind the ContentResolver, ContentProvider and Cursor mechanism present in Android. It seems like the only reason we do this is because the data we're passing around and updating is very complex and would be difficult to represent in a monolithic sqlite database and access via the rows/columns interface of a Cursor.
Has anyone adapted the existing Android data provider system to return data Objects based on the data in a cursor and then keep those objects up to date when the backing data store changes? Me naive approach would be to store serialized versions of these objects in a BLOB column in a sqlite table and wrap the cursor with an iterable deserializer mechanism, but I would rather not deserialize the objects into memory until I absolutely had to. I'd love to hear from others that have had to do something similar. -- 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
