Well, yes, one could do that, but it seems redundant, since SQLiteOpenHelper is already providing a singleton access to the database. All your proposal adds is singleton access to its Context on top of that. In fact, it might actually make the code more readable if ydm adds his own singleton for only that Context, and then always does the getInstance() on that context in the call to whatever class he defines as extending SQLiteOpenHelper.
At least that way the reader will not be misled by the redundancy. On Feb 22, 2:46 am, Kostya Vasilyev <kmans...@gmail.com> wrote: > 22.02.2011 13:32, ydm пишет: > > > I'm curious why the SQLite db requires a Context object, > > The database class doesn't - SQLiteOpenHelper (subclass) does, to get > the location of the database file. > > > and what I > > should do to share the same instance of a db object between many > > activities? Should I initialize it in the first activity and use it > > across the application, or may be any activity should reinitialize the > > db with itself as db context? > > If you're not going to implement a private content provider (which is > one way), I'd use a simple singleton, keeping a reference to one and > only SQLiteOpenHelper subclass object, initialized with the application > context. > > -- Kostya > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com -- 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
