0034115: ad_db_modified does not take into account check constraints

Description

The ad_db_modified function checks if the database has local changes. The problem is that it is not detecting changes done on check constraints. If a check constraint is added/modified/deleted, invoking ad_db_modified will return 'N', even though there are indeed local changes in the database.

Steps To Reproduce

- Run update.database to make sure there are no local changes.
- Check it executing this in the database: SELECT AD_DB_MODIFIED('N') FROM DUAL. It will return 'N' (this is OK)
- Remove a check constraint, for instance: ALTER TABLE c_order DROP CONSTRAINT c_order_isactive_check;
- Run again the function that checks if there are local changes: SELECT AD_DB_MODIFIED('N') FROM DUAL. It will return 'N' (this is WRONG, the database has local changes).
- Remove a foreign key, for instance: ALTER TABLE c_order DROP CONSTRAINT c_order_ad_client;
- Run again the function that checks if there are local changes: SELECT AD_DB_MODIFIED('N') FROM DUAL. It will return 'Y' (this is OK)

Proposed Solution

I am not sure, as taking now into account the check constraints will modify the checksum, and false positives in the detection of local changes will occur.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of	defect	0028644		acknowledged	Triage Platform Base	update.database doesn't detect check constraint modifications as local changes
related to	defect	0035628		closed	alostale	ORA: sometimes update.database after install.source detects db changes

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2016-09-28 11:14	AugustoMauch	New Issue
2016-09-28 11:14	AugustoMauch	Assigned To	=> platform
2016-09-28 11:14	AugustoMauch	Modules	=> Core
2016-09-28 11:14	AugustoMauch	Triggers an Emergency Pack	=> No
2016-09-29 09:14	alostale	Status	new => acknowledged
2017-03-28 10:19	alostale	Relationship added	related to 0035628
2019-07-30 15:17	alostale	Status	acknowledged => scheduled
2019-07-30 15:17	alostale	Relationship added	duplicate of 0028644
2019-07-30 15:17	alostale	Status	scheduled => closed
2019-07-30 15:17	alostale	Resolution	open => duplicate