I came to know today "THE TRUTH". i didnt knew it bfore :-)
Oracle APPS do not use Primary Key and Foreign Key constraints.
They use not null and unique indexes for primary key type columns.
Also they do not keep database triggers.
All the integrity is maintained thru application.
The PK,FK and triggers are not kept cos of performance reasons.
I am fighting with my client which wants to implement versioning for each
row and across relationship.
so if a dept attribute changes a new row shld be created and all dependents
shld be somehow made aware of the change. Also if an employee attribute
changes, a new employee version to be maintained while keeping the
relationship with the dept.
The only solution coming to my mind is keeping a surrogate key for every
table.
Guys do ull hv any IMPLEMENTED WORKING solution?
i can see my weekend....:(
-Mandar
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Mandar Ghosalkar
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
