meta_where 0.9.10 → 1.0.0

data/CHANGELOG

@@ -1,3 +1,6 @@
+Changes since 0.9.10 (2011-01-06):
+  * Doc updates only, and a version change to 1.0.0.
+
 Changes since 0.9.9 (2010-11-15):
   * Multiple conditions on the same column with the same predicate will be "OR"ed
     instead of dropping all but the last one. This tracks the same behavior in

data/README.rdoc

@@ -283,6 +283,47 @@ mapping," above) and also some convenience methods for ascending and descending
      ORDER BY  "articles"."title" DESC,
        "comments"."created_at" ASC, "comments"."updated_at"
 
+== Polymorphic belongs_to joins
+
+Polymorphic associations provide great flexibility, but they can sometimes be a bit of a hassle
+when it comes to querying through a belongs_to association. First, you have to know what type
+you're looking for to do a proper join, and then, you're forced into using a string join in order
+to make it happen (which would prevent the use of MetaWhere intelligent condition mapping).
+
+MetaWhere allows you to join polymorphic belongs_to associations like this:
+
+  Note.joins(:notable.type(Developer)).
+       where(:notable.type(Developer) => {:name.matches => 'Ernie%'})
+  => SELECT "notes".* FROM "notes"
+     INNER JOIN "developers" ON "developers"."id" = "notes"."notable_id"
+       AND "notes"."notable_type" = 'Developer'
+     WHERE "developers"."name" LIKE 'Ernie%'
+
+== Using ActiveRecord objects as condition values
+
+Wouldn't it be nice if you could do something like this?
+
+  # Developer belongs_to Company
+  company = Company.find(123)
+  Developer.where(:company => company)
+
+  # Developer HABTM Projects
+  projects = [Project.first, Project.last]
+  Developer.joins(:projects).where(:projects => projects)
+
+  # Note belongs_to :notable, :polymorphic => true
+  dev1 = Developer.first
+  dev2 = Developer.last
+  project = Project.first
+  company = Company.first
+  Note.where(:notable => [dev1, dev2, project, company]).to_sql
+  => SELECT "notes".* FROM "notes" WHERE (((("notes"."notable_id" IN (1, 8)
+     AND "notes"."notable_type" = 'Developer') OR ("notes"."notable_id" = 1
+     AND "notes"."notable_type" = 'Project')) OR ("notes"."notable_id" = 1
+     AND "notes"."notable_type" = 'Company')))
+
+With MetaWhere, you can.
+
 == Thanks
 A huge thank you goes to Pratik Naik (lifo) for a dicussion on #rails-contrib about a patch
 I'd submitted, and his take on a DSL for query conditions, which was the inspiration for this

data/VERSION

@@ -1 +1 @@
-0.9.10
+1.0.0

data/meta_where.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{meta_where}
-  s.version = "0.9.10"
+  s.version = "1.0.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Ernie Miller"]
-  s.date = %q{2011-01-06}
+  s.date = %q{2011-01-17}
   s.description = %q{
       MetaWhere offers the ability to call any Arel predicate methods
       (with a few convenient aliases) on your Model's attributes instead

metadata

@@ -3,10 +3,10 @@ name: meta_where
 version: !ruby/object:Gem::Version 
   prerelease: false
   segments: 
+  - 1
   - 0
-  - 9
-  - 10
-  version: 0.9.10
+  - 0
+  version: 1.0.0
 platform: ruby
 authors: 
 - Ernie Miller
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-01-06 00:00:00 -05:00
+date: 2011-01-17 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency