<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,3 +1,7 @@
+== 2.1.3
+
+* Added a no conflic resolution for other libraries already using the &quot;search&quot; method. If you have a conflict, use &quot;searchlogic&quot;.
+
 == 2.1.2 released 2009-07-04
 
 * Undefine the id method for the Search class, so that it acts like a condition.</diff>
      <filename>CHANGELOG.rdoc</filename>
    </modified>
    <modified>
      <diff>@@ -199,6 +199,16 @@ Instead of recreating the wheel with pagination, Searchlogic works great with wi
 
 If you don't like will_paginate, use another solution, or roll your own. Pagination really has nothing to do with searching, and the main goal for Searchlogic v2 was to keep it lean and simple. No reason to recreate the wheel and bloat the library.
 
+== Conflicts with other gems
+
+You will notice searchlogic wants to create a method called &quot;search&quot;. So do other libraries like thinking sphinx, etc. So searchlogic has a no conflict resolution. If the &quot;search&quot; method is already taken the method will be called &quot;searchlogic&quot; instead. So instead of
+
+  User.search
+
+You would do:
+
+  User.searchlogic
+
 == Under the hood
 
 Before I use a library in my application I like to glance at the source and try to at least understand the basics of how it works. If you are like me, a nice little explanation from the author is always helpful:</diff>
      <filename>README.rdoc</filename>
    </modified>
    <modified>
      <diff>@@ -14,6 +14,16 @@ ActiveRecord::Base.extend(Searchlogic::NamedScopes::Associations)
 ActiveRecord::Base.extend(Searchlogic::NamedScopes::AliasScope)
 ActiveRecord::Base.extend(Searchlogic::Search::Implementation)
 
+# Try to use the search method, if it's available. Thinking sphinx and other plugins
+# like to use that method as well.
+if !ActiveRecord::Base.respond_to?(:search)
+  ActiveRecord::Base.class_eval do
+    class &lt;&lt; self
+      alias_method :search, :searchlogic
+    end
+  end
+end
+
 if defined?(ActionController)
   require &quot;searchlogic/rails_helpers&quot;
   ActionController::Base.helper(Searchlogic::RailsHelpers)</diff>
      <filename>lib/searchlogic.rb</filename>
    </modified>
    <modified>
      <diff>@@ -17,8 +17,11 @@ module Searchlogic
   class Search
     # Responsible for adding a &quot;search&quot; method into your models.
     module Implementation
-      # Returns a new Search object for the given model.
-      def search(conditions = {})
+      # Additional method, gets aliases as &quot;search&quot; if that method
+      # is available. A lot of other libraries like to use &quot;search&quot;
+      # as well, so if you have a conflict like this, you can use
+      # this method directly.
+      def searchlogic(conditions = {})
         Search.new(self, scope(:find), conditions)
       end
     end</diff>
      <filename>lib/searchlogic/search.rb</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>23c82ce972278ed45824365b233ef1f61e7bac13</id>
    </parent>
  </parents>
  <author>
    <name>binarylogic</name>
    <email>bjohnson@binarylogic.com</email>
  </author>
  <url>http://github.com/binarylogic/searchlogic/commit/a60fc657e6f693423339c00f34058af63eeb4b39</url>
  <id>a60fc657e6f693423339c00f34058af63eeb4b39</id>
  <committed-date>2009-07-06T10:39:08-07:00</committed-date>
  <authored-date>2009-07-06T10:39:08-07:00</authored-date>
  <message>* Added a no conflic resolution for other libraries already using the &quot;search&quot; method. If you have a conflict, use &quot;searchlogic&quot;.</message>
  <tree>aede9d3ff6382db5c8d2f9f622e9685878cd70e0</tree>
  <committer>
    <name>binarylogic</name>
    <email>bjohnson@binarylogic.com</email>
  </committer>
</commit>
