Re: Keeping constraint names with export / import

From: Eric Givler <egivler_at_flash.net>
Date: Thu, 11 Jan 2001 02:32:06 GMT
Message-ID: <GW876.1678$J%.198633_at_news.flash.net>


I thought an import on this would preserve the user-named constraints?

Can you tell me what version you are using, and if you ran a show=y, prior to the command to log the creation of the constraints?

What's in that file for the constraints?

Do you have to export the constraints as a SECOND EXPORT, and then import them during a second pass?

Oh yeah.... Just what you wanted... More questions!

<aharris1_at_my-deja.com> wrote in message news:93ibr0$9me$1_at_nnrp1.deja.com...
> We have created more meaningful constraint names in our database in
> order to get more useful error messages. For example, a primary key
> constraint would be named PK#table1#field1, to show that the primary
> key (PK) exists on "table1" on the "field1" column. Or a not null
> constraint would be table1#field1#NOT_NULL, to show that the "field1"
> column of "table1" has a NOT NULL constraint. This helps to indicate
> the source of the error when an error message is printed that includes
> the constraint name.
Received on Thu Jan 11 2001 - 03:32:06 CET

Original text of this message