Lonzo1968 wrote: > I got you book from commonsware.com. I like what you have done so far, > especially the detail on the layouts.
Thanks! > 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). Well, hackbod responded on this question, and she's *WAY* more authoritative than I am on Android. I'd follow her recommendations. -- 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 -~----------~----~----~----~------~----~------~--~---
