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

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Add additional text to NotImplementedErrors [#6328 state:resolved]	Mike Gehard	2011-03-12	1	-1/+1
\| \| \| \|	Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
*	Use proper objects to do the work to build the associations (adding methods, ↵	Jon Leighton	2011-02-21	1	-0/+16
\| \| \| \|	callbacks etc) rather than calling a whole bunch of methods with rather long names.
*	Singular associations no longer use a proxy, so no need to check for the ↵	Jon Leighton	2011-02-21	1	-6/+0
\| \| \| \|	proxy type on assignment.
*	Associations - where possible, call attributes methods rather than directly ↵	Jon Leighton	2011-02-21	1	-1/+1
\| \| \| \|	accessing the instance variables
*	Split AssociationProxy into an Association class (and subclasses) which ↵	Jon Leighton	2011-02-18	1	-2/+2
\| \| \| \|	manages the association, and a CollectionProxy class which is only a proxy. Singular associations no longer have a proxy. See CHANGELOG for more.
*	Let's be less blasé about method visibility on association proxies	Jon Leighton	2011-01-30	1	-0/+1
\|
*	We shouldn't be using scoped.scoping { ... } to build associated records, as ↵	Jon Leighton	2011-01-30	1	-6/+9
\| \| \| \|	this can affect validations/callbacks/etc inside the record itself [#6252 state:resolved]
*	find_target can also go into SingularAssociation	Jon Leighton	2011-01-16	1	-0/+4
\|
*	Abstract a bit more into SingularAssociation	Jon Leighton	2011-01-16	1	-0/+6
\|
*	Abstract common code from BelongsToAssociation and HasOneAssociation into ↵	Jon Leighton	2011-01-16	1	-0/+31
	SingularAssociation