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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Easy dependent_restrict error message	Paco Guzman	2012-01-31	2	-4/+2
\|
*	has_many/has_one, :dependent => :restrict, deprecation added.	Manoj	2012-01-29	3	-3/+35
\|
*	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.
*	Remove Array.wrap calls in ActiveRecord	Rafael Mendonça França	2012-01-06	1	-2/+2
\|
*	Removed metaclass from the has_many dependency destroy method. Fixes #2954	Dmitry Polushkin	2011-12-31	2	-8/+5
\|
*	Deprecate implicit eager loading. Closes #950.	Jon Leighton	2011-12-29	1	-1/+1
\|
*	Fix #3672 again (dependent: delete_all perf)	Jon Leighton	2011-12-14	2	-2/+8
\|
*	avoid warnings	Josh Susser	2011-11-27	6	-15/+15
\| \| \| \| \| \| \|	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	2	-7/+13
\|
*	association methods are now generated in modules	Josh Susser	2011-11-15	7	-30/+25
\| \| \| \| \| \| \| \| \| \|	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.
*	Destroy association habtm record before destroying the record itself. Fixes ↵	Tomas D'Stefano	2011-07-08	1	-12/+10
\| \| \| \|	issue #402.
*	Removes the restriction on primary key when joining in a habtm && test that ↵	Mohammad El-Abid	2011-05-26	1	-4/+0
\| \| \| \|	it was properly removed
*	removed deprecated methods, and related tests, from ActiveRecord	Josh Kalderimis	2011-05-25	1	-13/+0
\|
*	Add block setting of attributes to singular associations	Andrew White	2011-05-17	1	-6/+6
\|
*	Bring back obj.association_loaded? as a deprecated method. Fixes #472.	Jon Leighton	2011-05-11	1	-0/+13
\|
*	Remove `#among?` from Active Support	Prem Sichanugrist	2011-04-13	3	-3/+3
\| \| \| \| \| \|	After a long list of discussion about the performance problem from using varargs and the reason that we can't find a great pair for it, it would be best to remove support for it for now. It will come back if we can find a good pair for it. For now, Bon Voyage, `#among?`.
*	Change Object#either? to Object#among? -- thanks to @jamesarosen for the ↵	David Heinemeier Hansson	2011-04-12	3	-3/+3
\| \| \| \|	suggestion!
*	Using Object#in? and Object#either? in various places	Prem Sichanugrist	2011-04-11	3	-3/+9
\| \| \| \|	There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
*	Make clearing of HABTM join table contents happen in an after_destory callback.	Murray Steele	2011-03-23	1	-12/+12
\| \| \| \|	The old method of redefining destroy meant that clearing the HABTM join table would happen as long as the call to destroy succeeded. Which meant if there was a before_destroy that stopped the instance being destroyed using normal means (returning false, raising ActiveRecord::Rollback) rather than exceptional means the join table would be cleared even though the instance wasn't destroyed. Doing it in an after_destroy hook avoids this and has the advantage of happening inside the DB transaction too.
*	Use proper objects to do the work to build the associations (adding methods, ↵	Jon Leighton	2011-02-21	7	-0/+430
	callbacks etc) rather than calling a whole bunch of methods with rather long names.