Does RAILS ensure that multiple users of a RAILS application won’t
create a
corrupt database
if each user is creating database entries with foreign keys linking
multiple tables together?
Do you have to use explicit table locking ?
Thanks,
P.
Does RAILS ensure that multiple users of a RAILS application won’t
create a
corrupt database
if each user is creating database entries with foreign keys linking
multiple tables together?
Do you have to use explicit table locking ?
Thanks,
P.
On Oct 15, 10:44am, “[email protected]” [email protected] wrote:
Does RAILS ensure that multiple users of a RAILS application won’t create a
corrupt database
if each user is creating database entries with foreign keys linking
multiple tables together?Do you have to use explicit table locking ?
Rails doesn’t do anything by default. You can use optimistic or
pessimistic locking of rows if you need to guard against concurrent
modifications to a single row. I’ve never needed table level locking
(which is an obvious scalability bottleneck)
I personally always use foreign key constraints to enforce integrity
of those references
Fred
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs