Mark Murphy wrote: > Another thing to consider with large yet simple database structures is > whether SQLite is the right answer at all. This is particularly true if > the data is read-only or read-mostly. It may be you are better served > finding a Java library implementing a lower-level data structure > (red-black tree, AVL tree, etc.) that is better tuned for your scenario. > You might even find one that can work efficiently with an InputStream, > thereby allowing you to keep the data in the APK without a second copy. > > For example, when I see "large word dictionary", I think of > spell-checkers, and implementing a spell-checker with a SQLite backend > would seem likely to have poor performance. Of course, then again, it's > been about two decades since I wrote my last spell-checker... > >
Mark, I observed that you are the author of two books on android (one yet to be released). I currently own a book on android by another author and I'm somewhat disappointed. It's rather superficial and lacks depth of discussion on issues like this, and actually skips a lot of simple features as well. How in-depth do you go in your books, especially in demonstrating best-practices of common tasks such as managing large amounts of data on such a small platform? Also, how are the two books related? Does the second book supersede the first, or are they companions? I'd like to buy both .... but I'm on a tight budget. Justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
