Thanks Mark, I got you book from commonsware.com. I like what you have done so far, especially the detail on the layouts.
What is the best architecture for this ContentProvider situation? Should I have a Provider for each table or muliple tables in a single provider. Maybe I'm missing something here, since I'm used to very different database layers (like the DAO pattern for example). On Aug 25, 5:48 pm, "Mark Murphy" <[EMAIL PROTECTED]> wrote: > > Since the ContentProvider interface has a > > single insert, update, query, delete methods, and as far as I can see, > > you can only include one ContentProvider in your application. > > ContentProviders are managed by their MIME type/URI patterns. An > application should be able to have several providers, or a singleprovider > that handles several sorts of data. > > If you want a single ContentProvider to handle multiple URI patterns, use > a UriMatcher: > > http://code.google.com/android/reference/android/content/UriMatcher.html > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.1 Published! --~--~---------~--~----~------------~-------~--~----~ 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 Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
