| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
hash for the through record, because the creation is done directly on the through association, which will already handle setting the conditions.
|
| |
|
| |
|
| |
|
|
|
|
| |
should return self.
|
|
|
|
| |
#replace which was previously incorrect, but the test passed due to the fact that to_a was not duping.
|
|
|
|
| |
is converted to SQL
|
|
|
|
| |
calculate
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
find(:last, ...)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
this can affect validations/callbacks/etc inside the record itself [#6252 state:resolved]
|
|
|
|
| |
consistency fix
|
|
|
|
| |
table. This has been documented as deprecated behaviour since April 2006. Please use has_many :through instead. A deprecation warning will be added to the 3-0-stable branch for the 3.0.4 release.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
SingularAssociation
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
inside the conditional
|
| |
|
| |
|
| |
|
|
|
|
| |
[#6257 state:resolved]
|
| |
|
| |
|
| |
|