Sean Griffin 3327cd3f61 Expand the number of types which can use prepared statements ... This will allow all types which require no additional handling to use prepared statements. Specifically, this will allow for `true`, `false`, `Date`, `Time`, and any custom PG type to use prepared statements. This also revealed another source of nil columns in bind params, and an inconsistency in their use. The specific inconsistency comes from a nested query coming from a through association, where one of the inversed associations is not bi-directional. The stop-gap is to simply construct the column at the site it is being used. This should simply go away on its own once we use `Attribute` to represent them instead, since we already have all of the information we need.		2015-01-24 21:07:55 -07:00
..
predicate_builder	Remove unneeded requires	2015-01-04 12:11:03 -03:00
batches.rb	Remove all cases of manuallly wrapping Arel::Nodes::Quoted	2014-12-29 11:21:56 -07:00
calculations.rb	Remove support to activerecord-deprecated_finders	2015-01-02 12:06:24 -03:00
delegation.rb	Remove unneeded require 'as/deprecation'	2015-01-04 07:45:07 -08:00
finder_methods.rb	Don't remove join dependencies in Relation#exists?	2015-01-23 12:05:14 -07:00
merger.rb	Don't duplicate Relation::VALUE_METHODS in Relation::Merger	2015-01-24 18:49:49 -07:00
predicate_builder.rb	Expand the number of types which can use prepared statements	2015-01-24 21:07:55 -07:00
query_methods.rb	Expand the number of types which can use prepared statements	2015-01-24 21:07:55 -07:00
spawn_methods.rb	Inject the PredicateBuilder into the Relation instance	2014-12-26 13:53:56 -07:00