Mister ics wrote:
> >
> > The behaviour is correct according to the SQL specifications.
> > RESTRICT (as well as NO ACTION) means, you cannot change the
> > primary key value of the referenced row. All other values can
> > be changed of course.
> >
> > So an attempt to
> >
> >
>
> The behaviour is correct according to the SQL specifications.
> RESTRICT (as well as NO ACTION) means, you cannot change the
> primary key value of the referenced row. All other values can
> be changed of course.
>
> So an attempt to
>
> UPDATE t1 SET id = 2 WHERE
Mister ics wrote:
> Hi,
>
> I'm a little confused by the "on update restrict" option in a referential
> integrity constraint. I don't know if i have not understood the meaning of
> this statement or it does not work properly.
> I think that if it is specified ON UPDATE RESTRICT in a foreign key
>
Hi,
I'm a little confused by the "on update restrict" option in a referential
integrity constraint. I don't know if i have not understood the meaning of
this statement or it does not work properly.
I think that if it is specified ON UPDATE RESTRICT in a foreign key
costraint, the sql-server sh
