Refactor #21639
closed
unique constraints should be enforced in the DB as well
Added by Tomer Brisker about 7 years ago.
Updated over 3 years ago.
Description
ActiveRecord unique constraints might not be properly enforced when Foreman is run in multiple processes due to "Time of Check - Time of Use" errors.
All unique constraints should also be enforced by database index constraints which will prevent invalid duplicate entries.
- Blocked by Bug #21766: Duplicate entries in taxable_taxonomies table added
- Blocked by Bug #21926: Compute-resource image creation allows duplicate name added
Tomer Brisker wrote:
ActiveRecord unique constraints might not be properly enforced when Foreman is run in multiple processes due to "Time of Check - Time of Use" errors.
All unique constraints should also be enforced by database index constraints which will prevent invalid duplicate entries.
I can see both the subtasks are completed, should we close this tracker?
- Status changed from New to Resolved
good point, closing this one.
Also available in: Atom
PDF
Updated by 
Updated by