Bug: Problems with multiple scopes beginning with the same name

[binarylogic]

Bug: Problems with multiple scopes beginning with the same name

Bug: Problems with multiple scopes beginning with the same name

I am trying to create a failing test for this in my test suite and can’t seem to do it. Do you mind giving that a shot. I am 90% certain this has to do with the order of keywords in the regular expression. Ex:

/(documents|documents_involved)/

When it should be

/(documents_involved|documents)/

This is a really easy fix, but I want to get a failing test in place first.

by Ben Johnson

Bug: Problems with multiple scopes beginning with the same name

This has got a little bit more complicated because the bug has changed since searchlogic 2.3.3. Now it occurs not every time. I can’t reproduce it and can’t write a failing test, sorry. But it seems that it has something to do with other calls to Contact.search BEFORE - very strange.

But I have found a very similar issue, perhaps they are related. Here is a small patch for the specs (just add one line) and the specs will fail:

@@@
diff --git a/vendor/plugins/searchlogic/spec/spec_helper.rb b/vendor/plugins/searchlogic/spec/spec_helper.rb
index a2b98f0..c155938 100644
--- a/vendor/plugins/searchlogic/spec/spec_helper.rb
+++ b/vendor/plugins/searchlogic/spec/spec_helper.rb
@@ -71,6 +71,7 @@ Spec::Runner.configure do |config|
class User < ActiveRecord::Base
belongs_to :company, :counter_cache => true
has_many :orders, :dependent => :destroy

•  has_many :orders_big, :class_name => ’Order’, :conditions => ’total > 100’
  

  end

  class Order < ActiveRecord::Base
  @@@

  by Georg Ledermann

[ledermann]

Seems to be fixed by c8547d5. Thanks!

Thanks