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

	Commit message (Collapse)	Author	Age	Files	Lines
*	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.