3.0.0 - 3.0.1 required 'namespace/model' 3.0.2 - 3.0.5 required 'namespace.model' (nested). It has the advantage of keeping the i18n file DRY when multiple models are in the same namespace, but can lead to translation key conflicts if models are nested within models. [#6448, #5572]
…ions in an AssociationProxy. This was recently removed and when a has_one association with conditions is eager loaded the conditions would be sanitized once for every result row, causing a database hit to fetch the columns.
This reverts commit e2523ff.
…:resolved] This will make the output of `rake routes` to be correctly match to the behavior of the application, as the regular expression used to match the path is greedy and won't capture the format part by default This commit is the second attempt on fixing the issue, as the regular expression on another commit on `master` was invalid.
…od aliased to the attribute name so it can be overridden but still called internally.
…template, test included Signed-off-by: Santiago Pastorino <email@example.com>
The method_name argument is "default_render" for implicit actions so use the action_name attribute to determine which callbacks to run. [#5673 state:resolved]
…ed value on write. Also remove read method reload arg on timezone attributes.
… callback. 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.
…when a model is destroyed but the destruction is blocked by a before_destroy.
…e! [#6559 state:resolved]
…less than 1 but greater than -1 [#6576 state:resolved] Signed-off-by: Santiago Pastorino <firstname.lastname@example.org>