rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Go through normal `where` logic when preloading associations	Sean Griffin	2014-12-26	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	This will allow eager type casting to take place as needed. There doesn't seem to be any particular reason that the `in` statement was forced for single values, and the commit message where it was introduced gives no context. See https://github.com/rails/rails/commit/d90b4e2615e8048fdeffc6dffe3246704adee01f
*	Build fix when running in isolation	Arun Agrawal	2014-11-14	1	-0/+1
\| \| \| \| \|	`Computer` class needs to be require See #17217 for more details
*	Don't test PostgreSQL implementation details	Akira Matsuda & Kohei Suzuki	2014-08-29	1	-3/+0
\| \| \| \| \|	Asserting that the message contains "QUERY PLAN" is enough for the adapter's test. The plan may vary according to number of tuples etc. but that's out of our concern.
*	remove the bind visitor since the collector handles substituting bind values	Aaron Patterson	2014-04-09	1	-3/+3
\|
*	match against bind values	Aaron Patterson	2014-01-14	1	-2/+2
\|
*	let EXPLAIN use a thread locals registry [John J. Wang & Xavier Noria]	Xavier Noria	2013-04-16	1	-7/+0
\| \| \| \|	Closes #10198.
*	Fix GH #5430. A Payload name for schema_search_path should be SCHEMA.	kennyj	2012-03-15	1	-0/+7
\|
*	add the query to AR::Relation#explain output	Xavier Noria	2011-11-25	1	-0/+3
\| \| \| \| \| \| \|	Rationale: this is more readable if serveral queries are involved in one call. Also, it will be possible to let AR log EXPLAINs automatically in production mode, where queries are not even around.
*	implements AR::Relation#explain	Xavier Noria	2011-11-05	1	-0/+25
	This is a first implementation, EXPLAIN is highly dependent on the database and I have made some compromises. On one hand, the method allows you to run the most common EXPLAIN and that's it. If you want EXPLAIN ANALYZE in PostgreSQL you need to do it by hand. On the other hand, I've tried to construct a string as close as possible to the ones built by the respective shells. The rationale is that IMO the user should feel at home with the output and recognize it at first sight. Per database. I don't know whether this implementation is going to work well. Let's see whether people like it.