Hi Pat,
On Feb 16, 9:02 am, Pat Allan <[email protected]> wrote: > I don't think it's an issue with the module naming (the first solution > suggested). The issue is that the expected method for searching via > Sphinx (or Ferret, Solr, etc) is 'search' - and that's what your > relationship is called as well. One is always going to override another. Of course, I see this now. > Although, as I'm writing this... perhaps what we want to do is only > include the search method if an index is defined for that model (or a > superclass)? That means it'll be there when needed, but otherwise it's > kept out of sight. > > I'll try to code that up, but patches are welcome if you want to try > to beat me to it :) Here's my stab at it: http://github.com/crishoj/thinking-sphinx/tree/master Tests seem to pass. Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" 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/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
