Hi everyone,
I am happy to announce that Rails 4.2.3.rc1 and 4.1.12.rc1 have been
released.
If no regressions are found expect the final release this Thursday, on June
25, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me
Changing this method's name reeks of bikeshedding.
Any one with more than a day's worth of Rails experience knows the difference
between these two methods and how to use them.
In my experience, the return value for save is almost always checked.
If we deprecate save and then have only save!,
On 22 Jun 2015 15:24, pseidemann p...@zattoo.com wrote:
hello,
currently in rails you have two methods to save a record: `save` and
`save!`.
I think `save` is often used wrong because the return value is not always
checked.
even the documentation is not very clear about the subtle different
hello,
currently in rails you have two methods to save a record: `save` and
`save!`.
I think `save` is often used wrong because the return value is not always
checked.
even the documentation is not very clear about the subtle different about
the two methods. for `save` the first sentence is:
I think the documentation is very clear about this:
Saves the model.
If the model is new a record gets created in the database, otherwise
the existing record gets updated.
By default, save always run validations. If any of them fail the
action is cancelled and save returns false.
If it is not we
