| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
has_one and belongs_to
|
|
|
|
| |
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]
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
BelongsToPolymorphicAssociation because the conditions are added straight to the association_scope as of a few days ago
|
| |
|
|
|
|
| |
to define a create_association! method in a minute.
|
| |
|
|
|
|
| |
the code that need that can now just use association_proxy(:name).loaded?/target=
|
| |
|
| |
|
| |
|