When do I use save!, create! and update_attributes! in Rails?

ruby-on-rails activerecord transactions
CalebHC picture CalebHC · Nov 19, 2009 · Viewed 59k times · Source

I'm trying to figure out when to use the bang! versions for saving and updating records? I've read and heard that you don't need them if you're just saving one record or updating a single attribute, if you're confident nothing should go wrong, or to always use them outside of a controller. I guess I'm paranoid about having multiple things getting saved then something fails then there is incomplete data in the DB. The current Rails project I'm working on is over 50% complete and currently doesn't contain any bangs. I have some custom methods I'm calling in models that update or create multiple records and worry if they should be in some sort of transaction.

Sorry if this seems scattered but I'm just trying to figure how to use the saving capabilities in ActiveRecord correctly and make my life easier and little more stress free in the end. Thanks for your time.

Answer

Andy Gaskell picture Andy Gaskell · Nov 19, 2009

The main difference is how failed saves are handled. When updating an ActiveRecord class the ! version will raise an exception if the record is invalid.

I recommend reading the docs here - http://api.rubyonrails.org/classes/ActiveRecord/Base.html

Using transactions might also be something worth looking into - http://api.rubyonrails.org/classes/ActiveRecord/Transactions/ClassMethods.html

Related questions

How to set transaction isolation level using ActiveRecord connection?

I need to manage transaction isolation level on a per-transaction basis in a way portable across databases (SQLite, PostgreSQL, MySQL at least). I know I can do it manually, like that: User.connection.execute('SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE') ...…

Read More
How to drop columns using Rails migration

What's the syntax for dropping a database table column through a Rails migration?

Read More
Rails: select unique values from a column

I already have a working solution, but I would really like to know why this doesn't work: ratings = Model.select(:rating).uniq ratings.each { |r| puts r.rating } It selects, but don't print unique values, it prints all values, including …

Read More