Feature #2400
Add foreign keys on database level
Related issues
Associated revisions
fixes #2400 migration to remove orphaned records and add foreign keys constraints to database tables
fixes #2400 continuation - match all host STI classes when finding orphaned records
refs #2400 - add foreigner/immigrant dependencies to spec file
History
#1
Updated by Joseph Magen almost 10 years ago
- Status changed from New to Ready For Testing
#2
Updated by Joseph Magen over 9 years ago
#3
Updated by Dominic Cleal over 9 years ago
- Category set to DB migrations
- Target version set to 1.3.0
#4
Updated by Joseph Magen over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 4e057da28e8a21be87d3ea02c8b466f0cf36b758.
#5
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3202: Orphaned records migration should use delete_all for speed added
#6
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3097: foreign key error on deleting trend added
#7
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3194: Ugly errors when destroy actions are stopped by FKs added
#8
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3212: defer MySQL foreign key constraints for rake db:convert:prod2dev added
#9
Updated by Dominic Cleal over 9 years ago
- Related to Bug #2899: Unable to remove the ptable because it is still associated with the host added
#10
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3071: OS edit integration test failure with foreign keys added
#11
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3268: defer postgresql foreign key constraints for rake db:convert:prod2dev added
#12
Updated by Dominic Cleal over 9 years ago
- Related to Refactor #3539: Drop foreman-mysql added
refs #2400 clean up tests so there are no orphaned foreign keys