05 Aug '12, 1am

Episode 59: Optimistic Locking (revised)

There is a chance one user will unintentionally override someone else's changes if they update a record near the same time. One solution is to use optimistic locking. The updated_at column can also be used for this as shown.

Full article: http://railscasts.com/episodes/59-optimistic-locking-revised

Tweets

ASCIIcast 16 - Virtual Attributes (revised) (pro)

railscasts.com 05 Aug '12, 10pm

#16 Virtual Attributes (revised) Jul 20, 2012 | 11 minutes | Active Record , Forms Virtual attributes are a clean way to a...

Great post explaining how to implement optimistic locking with ActiveRecord.

Great post explaining how to implement optimist...

engineyard.com 24 Jul '12, 7pm

While this behavior is helpful, it doesn’t solve a more worrisome problem. Let’s say Billy comes to change that same vacat...

Episode 238: Mongoid (revised)

railscasts.com 29 Jul '12, 1am

#238 Mongoid (revised) Jul 28, 2012 | 9 minutes | Models , Plugins Mongoid is a Ruby gem for interacting with MongoDB. Her...