Yeah, we tried that at one stage, but we had a very complicated SELECT query with a whole bunch of other conditions bundled into it. It made more sense to do the entire find in SQL then try and split the query up into TS and SQL.
The other reason we couldn't use TS (for that query) is because in that same query, we had to find members based on their age. And from memory, Sphinx couldn't handle dates before 1970...or something. I remember a team mate of mine poking @pat about it, but we couldn't come up with a nice solution. -- *Keith Pitt* Web: http://www.keithpitt.com Twitter: @keithpitt Skype: keithpitt Phone: +61 432 713 987 On Thu, Jun 3, 2010 at 1:17 PM, Julio Cesar Ody <[email protected]> wrote: > > Oh! I almost forgot, we do actually do one tricky thing. We wrote a > plpgsql > > function that made it easier for us to find locations within a certain > > radius. > > Which, by the way, can be done in Sphinx (and Thinking Sphinx) too. > I'm assuming it's relevant since you said "finding". > > > -- > http://crazyhollywood.org > > -- > 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]<rails-oceania%[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.
