Schema Manager Snapshot Tool Not Storing "delete_rule" Property for Foreign Keys
Description
The Schema Manager Snapshot Tool in the DABOM application is experiencing an issue where it fails to store the "delete_rule" property for foreign keys in the generated schema snapshots. The "delete_rule" property is essential for defining the cascading behavior of foreign key constraints, and its absence in the snapshots can lead to inconsistencies and unexpected behavior in database management.
Steps to Reproduce
- Open the DABOM application.
- Access the Schema Manager Snapshot Tool.
- Generate a schema snapshot that includes tables with foreign keys.
- Inspect the generated schema snapshot file or contents.
- Observe that the "delete_rule" property is missing for the foreign keys.
Expected Result
The Schema Manager Snapshot Tool should include the "delete_rule" property in the generated schema snapshots, accurately representing the cascading behavior of foreign key constraints.
Priority/Severity
-
High (critical issue that significantly impacts functionality) -
Medium (impacts functionality but is not critical) -
Low (affects usability but doesn't hinder functionality)
Impact
The absence of the "delete_rule" property in schema snapshots may result in incorrect cascading behavior for foreign key constraints. This can potentially lead to data integrity issues and unexpected behavior during database operations.
Additional Information
The "delete_rule" property for foreign keys is an essential component of database schema management, particularly for defining how related records are affected when a referenced record is deleted. Its inclusion in schema snapshots is crucial for maintaining consistency between schema versions and ensuring accurate database management.
Please investigate and address this issue promptly to ensure the Schema Manager Snapshot Tool correctly captures and stores the "delete_rule" property for foreign keys in generated schema snapshots.