# Rails basic record locking

**URL:** <https://www.ruby-forum.com/t/rails-basic-record-locking/107136>\
**Category:** Rails\
**Created:** [June 18, 2007, 3:26pm UTC](https://www.ruby-forum.com/t/rails-basic-record-locking/107136 "2007-06-18T15:26:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitsmith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/9de053/32.png) [@bitsmith](https://www.ruby-forum.com/u/bitsmith)\
**Post date:** [June 18, 2007, 3:26pm UTC](https://www.ruby-forum.com/t/rails-basic-record-locking/107136/1 "2007-06-18T15:26:22Z")

</div>

…i’m a rails newbie…and before i get into rails whole hog… is  
rails capable of sensing that a main record is locked out by some one  
else and can it also sense a ‘race’ condition or ‘multi-record  
interlocking condition’ i will be using oracle not mysql…can rails  
prevent these…??? so if a user is updating main record with id=5 and  
another user tries to request id=5 at the same time will rails be  
‘smart’ enough to message this new user that record id=5 is busy? or if  
two users inadvertantly try to change a related reference record even  
though they have different ‘main record’ id# one will be ‘notified’ of  
this ‘race’ condition? …tia dave