Thanks Tristan - might go with the 2nd one for now :-) Chris
On May 30, 5:19 am, Tristan <tristan.slomin...@gmail.com> wrote: > I've implemented this on app engine: > > http://www.miislita.com/term-vector/term-vector-3.html > > limitations: > - need to store your own indexes, > - need to use task queue to work around 1MB put limit when creating / > updating indexes > - search is done in memory v. via queries > - might run out of time on extremely large searches (hasn't happened > yet) > > benefits: > - you can use entire paragraphs as search queries > - automatic matching of *like* terms as a consequence of using this > approach > > Another (simpler) way is described here: > > http://googleappengine.blogspot.com/2010/04/making-your-app-searchabl... > > limitations: > - Number of search terms is limited (to roughly 5). > - You have to make sure you are searching in a subset of the data with > less than ~200 results. > > benefits: > - fast and easy to implement > > On May 29, 12:30 pm, Khookie <chris.k...@gmail.com> wrote: > > > I know there's no official API for fulltext search, so I know I have > > to roll my own. > > > I was wondering if anyone has ideas or pointers on doing it, > > especially in GAE. Reference URLs, etc. will be appreciated. > > > Kind Regards > > > Chris -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
