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

**URL:** <https://www.ruby-forum.com/t/rails-convention-for-record-pseudo-locking-on-multi-user-s/113843>\
**Category:** Rails\
**Created:** [September 5, 2007, 2:55pm UTC](https://www.ruby-forum.com/t/rails-convention-for-record-pseudo-locking-on-multi-user-s/113843 "2007-09-05T14:55:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Philip\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@Philip\_N](https://www.ruby-forum.com/u/Philip_N)\
**Post date:** [September 5, 2007, 2:55pm UTC](https://www.ruby-forum.com/t/rails-convention-for-record-pseudo-locking-on-multi-user-s/113843/1 "2007-09-05T14:55:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Philip\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@Philip\_N](https://www.ruby-forum.com/u/Philip_N)\
**Post date:** [September 5, 2007, 3:11pm UTC](https://www.ruby-forum.com/t/rails-convention-for-record-pseudo-locking-on-multi-user-s/113843/2 "2007-09-05T15:11:45Z")

</div>

On Sep 5, 6:00 am, Philip N. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

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

[http://api.rubyonrails.com/classes/ActiveRecord/Locking.html](http://api.rubyonrails.com/classes/ActiveRecord/Locking.html)