Binarylogic Searchlogic

Comments and changes to this ticket

• You flagged this item as spam.
  

  Deepu March 23rd, 2009 @ 07:25 AM

  @Nico - If i am not wrong you want to include some conditions on the associated tables ? If so then this will do:-

  search = Measure.new_search search.conditions.measures_tags.x_gt = params[:x] search.conditions.tags.y_lt = params[:y] @results = search.all

  just make sure you have proper associations in the respective models.

  Am not sure whether i understood your problem correctly though

• You flagged this item as spam.
  

  Deepu March 23rd, 2009 @ 07:28 AM

  sorry above comment was formatted all lost. The code is

  @@@

   search = Measure.new_search search.conditions.measures_tags.x_gt = params[:x] search.conditions.tags.y_lt = params[:y] @results = search.all
  
  

• You flagged this item as spam.
  

  Deepu March 23rd, 2009 @ 07:28 AM

  damn this formatting.

  
  search = Measure.new_search; search.conditions.measures_tags.x_gt = params[:x];
  search.conditions.tags.y_lt = params[:y];
   @results = search.all
  

• You flagged this item as spam.
  

  Deepu March 23rd, 2009 @ 10:28 AM

  @nico :-

  try search.all(:include => "tags") . it worked for me.

  Cheers, Deepu.

• 

  Ben Johnson March 23rd, 2009 @ 05:26 PM

  • State changed from “new” to “open”

  I don't think this is searchlogic, I think ActiveRecord splits it up into multiple queries for performance reasons. Im fairly certain they made this change within the last 6 months or so. Try doing the query without searchlogic, i bet you get the same results.

• 

  Ben Johnson March 30th, 2009 @ 11:41 AM

  I am busy and have a job just like you. It would help me out if you could create a failing test, then I could quickly fix the issue and move on, instead of having to read through all of this. Or you could always try and fix it yourself. Thanks.

• You flagged this item as spam.
  

  Georg Ledermann May 22nd, 2009 @ 07:16 AM

  Stumbled upon the same problem. The :include options seems to be ignored. Hoping Ben has time to fix this... Perhaps this bug is another argument for building the version 2.0 of Searchlogic :)

• 

  Ben Johnson May 22nd, 2009 @ 10:33 AM

  Well it seems to be working for me:

  >> s = Neighborhood.new_search
  => #25}>
  >> s.include = :relationships
  => :relationships
  >> s.sanitize
  => {:limit=>25, :include=>:relationships}
  

  Also, I remember reading somewhere that AR changed how it treats that option. I might be way off here, but I think they lazily load those records because it was faster to perform a bunch of small queries than one big one.

• You flagged this item as spam.
  

  Georg Ledermann May 22nd, 2009 @ 10:52 AM

  Thank you for this hint, Ben!
  It seems there is difference in this two approaches:

  1)
  

   s = Neighborhood.new_search
   s.include = :relationships
   s.find :all
  

  => Works fine, the include option is given to AR

  2)
  

   s = Neighborhood.new_search
   s.find :all, :include => :relationships
  

  => Fails because it ignores the include option

• 

  Ben Johnson June 20th, 2009 @ 05:02 AM

  • State changed from “open” to “resolved”

  v2 should resolve this issue as it falls into the standard practices of using the :include option. Hope this helps. But the first example georg gave is correct.