Sorry - no answer - but exactly the same question. I've been browsing a number of examples from the books and they all show just one table - with a directory (list) access and an item access.
My feeling is the ContentProvider ought to warp the logical groupings of data, so if the tables are related then there would be one ContentProvider. However - I'm going back to read this again: http://developer.android.com/guide/topics/providers/content-providers.html especially the URI part... Interested to hear the opinions of others here too... Rgds, Nigel On Sep 11, 8:58 am, Android Box <[email protected]> wrote: > Hi all, > > When an application needs to use two or more SQLite tables, > will we need to separate differenceContentProvider(by table) to handle > them, > or just oneContentProviderto do it? > > Ryan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
