Rails Convention for "Record Pseudo Locking" on Multi-User S

We are writing an order processing system, where we will display a list
of
orders for clerks to process. Obviously we don’t want two people
working on
the same order. In other systems we’ve put a LOCKED_BY column in the
database which is set on entering the edit screen and unset on saving.

But is there a Rails convention, or Rails way, for doing this (before we
go
off and write our own code) ?

Thanks

Phil Nelson

On Sep 5, 6:00 am, Philip N. [email protected] wrote:

Phil Nelson
race conditions: you want to investigate optimistic and pessimistic
locking and transactions:

http://api.rubyonrails.com/classes/ActiveRecord/Locking.html

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs