Not simple, but a few other ideas.. Sunspot => http://sunspot.github.com/ - some people don't like it.. but it's worked for me.
However, lately I've been using Redis to create my own indexes - super duper fast, but you really need to think through what you are doing. Your mileage may vary. rgds, - amtt. On 15 February 2012 14:47, Dmytrii Nagirniak <[email protected]> wrote: > > On 14/02/2012, at 5:30 PM, Chris Berkhout wrote: > > Okay. I'm doing something similar at the moment with ElasticSearch > > (via the Tire gem). The trick is just having the right flags in the > > index and adding a filter (actually, a boolean query) based on the > > user's permissions when building the query. > > > > Exactly how you do it will depend on the details of your schema and > > data. If each user's data is completely separate, another option with > > ElasticSearch is to use a different index for each user. > > Thanks. It sounds like a reasonable approach to take. > > > > Not sure if there are other things that specifically address this use > > case. PG may allow you to do a join before applying the FTS part. PG > > in testing sounds fine to me, unless you have an inflexible CI > > environment to think about. > > As far as I can see the PG FTS is the most pragmatic approach for now. > Will probably take that route. > Now need to skip over my reading queue with a good PG book :) > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
