Re: referential intergrity

Hi,

    Short answer - cannot do as enabled. But...     You could disable the primary key and disable the not null constraint on the field and then perform the insert. But, of course, you couldn't reenable them - until you solved your problem. So, since this or any solution is temporary for this table to be inserted on (in it's present config) it would seem you might be better off giving the project_number something inocuous (project 999) until you perform the proper update after the initial insert. Just remember within the insert to give yourself something to choose on in your where clause of the update.
That'll be $.02. Greg

Tong Zhai wrote:

> Hi, all:
> we are setting up a db, one of the table is works_on, and the primary key
> for that table are composite of project_number and Employee_ssn, so by
> definition they can't be null, but if I do want to insert a record with
> null project_number, how can I do that ?
>
> tong.
Received on Thu Mar 05 1998 - 00:00:00 CST