Permalink
Browse files

Optimistic locking: lock_version needed type information.

  • Loading branch information...
1 parent a9398a7 commit 1f4f4d4ccb1fa5fa20779a54a0cbcc0b6699e87c @nprncbl nprncbl committed Apr 5, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 guides/source/active_record_querying.textile
@@ -695,7 +695,7 @@ Optimistic locking allows multiple users to access the same record for edits, an
<strong>Optimistic locking column</strong>
-In order to use optimistic locking, the table needs to have a column called +lock_version+. Each time the record is updated, Active Record increments the +lock_version+ column. If an update request is made with a lower value in the +lock_version+ field than is currently in the +lock_version+ column in the database, the update request will fail with an +ActiveRecord::StaleObjectError+. Example:
+In order to use optimistic locking, the table needs to have a column called +lock_version+ of type integer. Each time the record is updated, Active Record increments the +lock_version+ column. If an update request is made with a lower value in the +lock_version+ field than is currently in the +lock_version+ column in the database, the update request will fail with an +ActiveRecord::StaleObjectError+. Example:
<ruby>
c1 = Client.find(1)

0 comments on commit 1f4f4d4

Please sign in to comment.