searchlogic 2.3.1 → 2.3.2

data/CHANGELOG.rdoc

@@ -1,3 +1,8 @@
+== 2.3.2 relased 2009-08-26
+
+* Add in scope_procedure as an alias for alias_scope.
+* Fixed bug with not_blank condition.
+
 == 2.3.1 released 2009-08-24
 
 * Added blank and not_blank conditions.

data/README.rdoc

@@ -8,6 +8,7 @@ Searchlogic makes using ActiveRecord named scopes easier and less repetitive. It
 * <b>Repository:</b> http://github.com/binarylogic/searchlogic/tree/master
 * <b>Issues:</b> http://github.com/binarylogic/searchlogic/issues
 * <b>Google group:</b> http://groups.google.com/group/searchlogic
+* <b>Railscast:</b> http://railscasts.com/episodes/176-searchlogic
 
 <b>Before contacting me directly, please read:</b>
 
@@ -83,6 +84,8 @@ Typing out 'greater_than_or_equal_to' is not fun. Instead Searchlogic provides v
 
 This is my favorite part of Searchlogic. You can dynamically call scopes on associated classes and Searchlogic will take care of creating the necessary joins for you. This is REALY nice for keeping your code DRY. The best way to explain this is to show you:
 
+=== Searchlogic provided scopes
+
 Let's take some basic scopes that Searchlogic provides for every model:
 
   # We have the following relationships
@@ -100,14 +103,18 @@ Let's take some basic scopes that Searchlogic provides for every model:
 
 This is recursive, you can travel through your associations simply by typing it in the name of the method. Again these are just named scopes. You can chain them together, call methods off of them, etc.
 
+=== Custom associated scopes
+
 Also, these conditions aren't limited to the scopes Searchlogic provides. You can use your own scopes. Like this:
 
   LineItem.named_scope :expensive, :conditions => "line_items.price > 500"
   
-  User.orders_line_items_expensive(true)
+  User.orders_line_items_expensive
 
 As I stated above, Searchlogic will take care of creating the necessary joins for you. This is REALLY nice when trying to keep your code DRY, because if you wanted to use a scope like this in your User model you would have to copy over the conditions. Now you have 2 named scopes that are essentially doing the same thing. Why do that when you can dynamically access that scope using this feature?
 
+=== Uses :joins not :include
+
 Another thing to note is that the joins created by Searchlogic do NOT use the :include option, making them <em>much</em> faster. Instead they leverage the :joins option, which is great for performance. To prove my point here is a quick benchmark from an application I am working on:
 
   Benchmark.bm do |x|
@@ -163,6 +170,18 @@ You can do:
 
 Again, these just map to named scopes. Use Searchlogic's dynamic scopes, use scopes on associations, use your own custom scopes. As long as it maps to a named scope it will join the conditions with 'OR'. There are no limitations.
 
+== Create scope procedures
+
+Sometimes you notice a pattern in your application where you are constantly combining certain named scopes. You want to keep the flexibility of being able to mix and match small named scopes, while at the same time being able to call a single scope for a common task. User searchlogic's scpe procedure:
+
+  User.scope_procedure :awesome, lambda { first_name_begins_with("ben").last_name_begins_with("johnson").website_equals("binarylogic.com") }
+
+All that this is doing is creating a class level method, but what is nice about this method is that is more inline with your other named scopes. It also tells searchlogic that this method is 'safe' to use when using the search method. Ex:
+
+  User.search(:awesome => true)
+
+Otherwise searchlogic will ignore the 'awesome' condition because there is no way to tell that its a valid scope. This is a security measure to keep users from passing in a scope with a named like 'destroy_all'.
+
 == Make searching and ordering data in your application trivial
 
 The above is great, but what about tying all of this in with a search form in your application? What would be really nice is if we could use an object that represented a single search. Like this...
@@ -267,6 +286,8 @@ Before I use a library in my application I like to glance at the source and try
 
 Searchlogic utilizes method_missing to create all of these named scopes. When it hits method_missing it creates a named scope to ensure it will never hit method missing for that named scope again. Sort of a caching mechanism. It works in the same fashion as ActiveRecord's "find_by_*" methods. This way only the named scopes you need are created and nothing more.
 
+The search object is just a proxy to your model that only delegates calls that map to named scopes and nothing more. This is obviously done for security reasons. It also helps make form integration easier, by type casting values, and playing nice with form_for. This class is pretty simple as well.
+
 That's about it, the named scope options are pretty bare bones and created just like you would manually.
 
 == Credit

data/VERSION.yml

@@ -1,4 +1,4 @@
 --- 
 :minor: 3
-:patch: 1
+:patch: 2
 :major: 2

data/lib/searchlogic/named_scopes/alias_scope.rb

@@ -44,6 +44,7 @@ module Searchlogic
           end
         end
       end
+      alias_method :scope_procedure, :alias_scope
       
       def alias_scopes # :nodoc:
         @alias_scopes ||= {}

data/lib/searchlogic/named_scopes/conditions.rb

@@ -122,7 +122,7 @@ module Searchlogic
           when "blank"
             {:conditions => "#{table_name}.#{column} = '' OR #{table_name}.#{column} IS NULL"}
           when "not_blank"
-            {:conditions => "#{table_name}.#{column} != '' OR #{table_name}.#{column} IS NOT NULL"}
+            {:conditions => "#{table_name}.#{column} != '' AND #{table_name}.#{column} IS NOT NULL"}
           end
           
           named_scope("#{column}_#{condition}".to_sym, scope_options)

data/searchlogic.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{searchlogic}
-  s.version = "2.3.1"
+  s.version = "2.3.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Ben Johnson of Binary Logic"]
-  s.date = %q{2009-08-24}
+  s.date = %q{2009-08-26}
   s.description = %q{Searchlogic makes using ActiveRecord named scopes easier and less repetitive.}
   s.email = %q{bjohnson@binarylogic.com}
   s.extra_rdoc_files = [

data/spec/named_scopes/conditions_spec.rb

@@ -96,12 +96,12 @@ describe "Conditions" do
     
     it "should have blank" do
       ["bjohnson", "", nil].each { |username| User.create(:username => username) }
-      User.username_blank.all.should == User.all(:conditions => "username IS NULL OR username = ''")
+      User.username_blank.all.should == [User.find_by_username(""), User.find_by_username(nil)]
     end
     
     it "should have not blank" do
       ["bjohnson", "", nil].each { |username| User.create(:username => username) }
-      User.username_not_blank.all.should == User.all(:conditions => "username IS NOT NULL OR username != ''")      
+      User.username_not_blank.all.should == User.find_all_by_username("bjohnson")
     end
   end
   

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: searchlogic
 version: !ruby/object:Gem::Version 
-  version: 2.3.1
+  version: 2.3.2
 platform: ruby
 authors: 
 - Ben Johnson of Binary Logic
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-08-24 00:00:00 -04:00
+date: 2009-08-26 00:00:00 -04:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency