Aaron Blohowiak on 18 May 2007 20:18:09 -0000

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PhillyOnRails] Rails Resources and Search

Even with search food, you wouldnt get the time that you'd need.

YOu could get the ids from ferret, then refine the search using old fashioned methods 
( in[..] )

Aaron Blohowiak

On May 18, 2007, at 4:14 PM, Mike Zornek wrote:

On 5/16/07 9:08 PM, "Toby DiPasquale" <toby@cbcg.net> wrote:

On Wed, May 16, 2007 at 01:50:26PM -0400, Mike Zornek wrote:
Is there any best practice for introducing an index with search capabilities
for the resources design pattern introed in Rails 1.2? I have my own thing
working but I wonder if their is a better way.

Will acts_as_ferret work for you? Seems like a good solution, as its a
Ruby/C hybrid and actually faster than Lucene (the project on which it is
based). I know a lot of people are using it though I have no first-hand
experience with it personally.

For full text generic searching acts_as_ferret does look cool.

However, what I'm talking about here is a more line item search, like first
name is bob (STRING), has placed order in last 48 hours (TIME), is an
annoying customer (BOOL). It might even stretch to joins, has photo that is
unapproved etc.

Does Ferret do this? I suppose I could do a before save and produce search
food, like special keys (is_bad_customer:YES) in a text field to feed the
search. But that would prob get out of hand fast.

Maybe I'll bring it up at the meeting. Thanks.

~ Mike

To unsubscribe or change your settings, visit:

To unsubscribe or change your settings, visit: