Actually, N-Grams scale very efficiently. I wrote a simple mp3 library manager, that uses N-grams on the ID3 tags of my mp3 collection, which is well over 60GB. Storing the N-gram of every song's ID3 only takes up roughly 1MB of RAM, if that. I would say for anything web2py would be used for, N-gram based search would be kicken. (come to think of it, since I have the n-gram code in python anyways, plugin time :P). Unless you store as much data as a googlebot, I don't think you need to worry.
-Thadeus On Sun, Nov 29, 2009 at 9:41 PM, mdipierro <[email protected]> wrote: > You can but how well does it scale? to how many records? how long > strings? > > On Nov 29, 5:23 pm, Richard <[email protected]> wrote: > > to support full text search you can generate all the N-grams of each > > record and then stored then in a StringListProperty: > http://code.google.com/appengine/docs/python/datastore/typesandproper... > > > > On Nov 28, 6:20 am, vince <[email protected]> wrote: > > > > > i've notice the new DAL do support a form of LIKE on GAE. > > > > > anyone tried it and how's the performance? it seems to only support > > > "startwith", what about "contain"? > > > > > is there any experimental nosql database i can play with now besides > > > GAE? > > > > > -vince > > > > > > -- > > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<web2py%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
