Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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.

Related issues 2 (0 open — 2 closed)

Blocked by Foreman - Bug #21766: Duplicate entries in taxable_taxonomies tableClosedTomer Brisker11/26/2017Actions
Blocked by Foreman - Bug #21926: Compute-resource image creation allows duplicate nameClosedTomer Brisker12/11/2017Actions
Actions
Copy link
 #1

Updated by Tomer Brisker about 7 years ago

  • Blocked by Bug #21766: Duplicate entries in taxable_taxonomies table added
Actions
Copy link
 #2

Updated by Tomer Brisker about 7 years ago

  • Blocked by Bug #21926: Compute-resource image creation allows duplicate name added
Actions
Copy link
 #3

Updated by Amit Upadhye over 3 years ago

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?

Actions
Copy link
 #4

Updated by Tomer Brisker over 3 years ago

  • Status changed from New to Resolved

good point, closing this one.

Actions
Copy link

Also available in: Atom PDF