With more than one application server, validates_uniqueness_of becomes a lie. Two app servers -> two requests -> two near-simultaneous uniqueness checks -> two processes that commit to the database independently, violating this faux constraint. You'll need a database-level constraint for cases like these. consistency_fail will find your missing unique indexes, so you can add them and stop ignoring the C in ACID.
Required Ruby Version
>= 0
Authors
Colin Jones
Versions
- 0.3.7 October 22, 2018 (14.5 KB)
- 0.3.6 October 09, 2018 (14.5 KB)
- 0.3.5 February 01, 2017 (14 KB)
- 0.3.4 February 02, 2016 (14 KB)
- 0.3.3 December 12, 2014 (12.5 KB)