In article <fdeaab$vc0$1_at_news4.zwoll1.ov.home.nl>,
frank.van.bortel_at_gmail.com says...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hjr.pythian_at_gmail.com wrote:
> > On Sep 26, 4:35 am, Frank van Bortel <frank.van.bor..._at_gmail.com>
> > wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> not produce errors != constraint violations
> >> but more generic than that
> >> - --
> >> Regards,
> >> Frank van Bortel
> >>
> >
> > Bearing in mind that the original question was, "is Oracle smart
> > enough to import things in an order that will not produce errors?",
> > give me an error, Frank, that will be caused by changing the order of
> > import of tables which ISN'T a constraint violation.
> >
> > Creating indexes before the tables on which they're supposed to be
> > built doesn't count, because import has never been that stupid.
> >
> You miss the point.
>
> It's not just about constraints or the order of tables.
> The original question was more generic, and yes, sometimes
> you'll get errors because dependent objects do not
> (yet) exist: procedures, functions, packages and views to name
> a few, can either be invalid and need to be recompiled, or are
> not created at all, which can happen with views.
>
Woaw ! When is a view not created at all, Frank ?
Received on Wed Sep 26 2007 - 12:59:18 CDT
