On Thu, Apr 7, 2011 at 6:33 PM, Nathan <critter...@crittermap.com> wrote: > Would a shopping list application only allow you to have one shopping > list, called default? > A lame one would, yes.
A sensible implementation would use one database, with a "lists" table to identify the lists, and foreign key relationships in the other tables as needed back to the lists table. This is a fairly basic relational database design. > I really don't think my scenario is that outrageous. I would say that the code smell increases as the square of the number of databases. So, more than one database is not necessarily stinky, but 100 databases would certainly qualify as "outrageous" in my book. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
