Re: PUBLIC:Re: Duplicate check constraints on the same column

From: Keith Boulton <boulke_at_globalnet.co.uk>
Date: 1997/11/28
Message-ID: <347f3502.32911714@read.news.global.net.uk>#1/1

On Fri, 28 Nov 1997 13:04:10 +0100, Eugen Nyffeler <eugen.nyffeler_at_ubs.com> wrote:

>The problem is (or might be...) that Oracle creates the constraint names
>with a sequence number if there is no name supplied.
>If you do now an export of the schema (or table) without constraints=No,
>and you do an import into the same schema (without prior drop of the
>tables or constraints in this case), Oracle adds the same constraints
>again with a different sequence number (the reason is , is guess, that
>Oracle writes only the alter table statement add constrain(..) to the
>export file). in cases of named constraints Oracle would get an error
>during import when the name already exists.
>
>Hope not to confusing..
>
>eugen ;-)

I just experimented with this and it happens exactly as you said. I'm surprised that Oracle doesn't warn you if you add a constraint with the same text as a pre-existing constraint. Received on Fri Nov 28 1997 - 00:00:00 CST