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

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Same method for has_many and has_one associations	Paco Guzman	2012-01-31	1	-0/+15
\|
*	has_many/has_one, :dependent => :restrict, deprecation added.	Manoj	2012-01-29	1	-1/+15
\|
*	Deprecate inferred JOINs with includes + SQL snippets.	Jon Leighton	2012-01-16	1	-1/+1
\| \| \| \| \| \|	See the CHANGELOG for details. Fixes #950.
*	Revert "Deprecate implicit eager loading. Closes #950."	Jon Leighton	2012-01-16	1	-1/+1
\| \| \| \|	This reverts commit c99d507fccca2e9e4d12e49b4387e007c5481ae9.
*	Deprecate implicit eager loading. Closes #950.	Jon Leighton	2011-12-29	1	-1/+1
\|
*	avoid warnings	Josh Susser	2011-11-27	1	-2/+2
\| \| \| \| \| \| \|	This change uses Module.redefine_method as defined in ActiveSupport. Making Module.define_method public would be as clean in the code, and would also emit warnings when redefining an association. That is pretty messy given current tests, so I'm leaving it for someone else to decide what approach is better.
*	use GeneratedFeatureMethods module for associations	Josh Susser	2011-11-27	1	-3/+5
\|
*	association methods are now generated in modules	Josh Susser	2011-11-15	1	-5/+5
\| \| \| \| \| \| \| \| \| \|	Instead of generating association methods directly in the model class, they are generated in an anonymous module which is then included in the model class. There is one such module for each association. The only subtlety is that the generated_attributes_methods module (from ActiveModel) must be forced to be included before association methods are created so that attribute methods will not shadow association methods.
*	Use proper objects to do the work to build the associations (adding methods, ↵	Jon Leighton	2011-02-21	1	-0/+53
	callbacks etc) rather than calling a whole bunch of methods with rather long names.