Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Child records with no parent in 10.2.0.3

Re: Child records with no parent in 10.2.0.3

From: <ejwandersson_at_gmail.com>
Date: Thu, 04 Oct 2007 13:30:53 -0700
Message-ID: <1191529853.505790.69670@r29g2000hsg.googlegroups.com>


On Oct 4, 4:58 pm, "fitzjarr..._at_cox.net" <fitzjarr..._at_cox.net> wrote:
> On Oct 4, 8:57 am, "Richard Foote" <richard.fo..._at_nospam.bigpond.com>
> wrote (among other things):
>
>
>
> > However, putting a FK in disable validate is questionable to say the least?
>
> I agree entirely, however it is allowed by Oracle and, as such, one
> can create an undesirable situation of a valid FK constraint on a
> table containing orphaned data. Of course as Howard explained it's a
> limited-use option (designed for DW reloads, apparently).
>
> I simply wasn't expecting the outcome I received using 10.2.0.3.
>
> We live, we learn.
>
> David Fitzjarrell

I can understand how this "feature" is used during partition exchange in a DW-environment. But then as I understand it it's used on top of PK,UK and Check constraint.
And as these constraints does not reference any other tables + The fact that a DISABLE VALIDATED constraint protects that table from any DML =>
means the reference integrity is never in danger. So no problem there!

But as soon as we do this on FK constraint we put the reference integrity in danger.
And I can't really see why even a partition exchange or any other feature ever has to do this.
/ Wilhelm2000 Received on Thu Oct 04 2007 - 15:30:53 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US