Hi All,
Nobody has proposed this before so let me throw it out for discussion.
Think about a compromise between having and not having referential integrity
constraints. The approach is that during development and testing, all RIs are
enabled. But when you push to production, disable or drop all of them. The
advantage of not having or enabling RIs in production is not portability in
this case; it's performance instead, however marginal it is.
I think I read somewhere about Oracle's official answer to this little
performance hit due to RIs. Think about it. There must be some. It shouldn't be
hard to measure but I have not done it.
Yong Huang
[EMAIL PROTECTED]
you wrote:
We have a situation where are no relationships are
defined at the database level. i.e no foreign keys
constraints have established at the Database. The
application is still at the Development Stage.
Everything is controlled at the application level.
I as the DBA appose this design for Data security and
also cannot reverse engineer from the tables into
Designer.
Can you please share you pros / Cons.
Thanks
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: yong huang
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).
