On Tue, Dec 20, 2011 at 4:59 AM, Christopher Van Kirk <[email protected]> wrote: > Three points. > > 1) Building the searching functionality twice is far more expensive than > building it once, no matter what approach you use. Be sure that the > performance of the DB approach is acceptable before you go and build it that > way.
Okay. > 2) It can be quite challenging to get decent performance out of a database > for something like this, depending on the functionality required. If, for > example, you need real-time narrowing down of words, a database is going to > be very slow (e.g. as you type letters, you get an alphabetized list of > what's in the db). True.. > 3) There's probably an open source Trie out there somewhere that you can > just use. > Right, which is what I suggested in the first place if he goes this direction.. http://wikipedia-clustering.speedblue.org/trieJava.php kris -- 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
