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

  1. 0.3.7
    1. source

      1. 0.3.7 source October 22, 2018 (14.5 KB)
  2. 0.3.6
    1. source

      1. 0.3.6 source October 09, 2018 (14.5 KB)
  3. 0.3.5
    1. source

      1. 0.3.5 source February 01, 2017 (14 KB)
  4. 0.3.4
    1. source

      1. 0.3.4 source February 02, 2016 (14 KB)
  5. 0.3.3
    1. source

      1. 0.3.3 source December 12, 2014 (12.5 KB)
Show all versions (13 total)

SHA 256 checksum