pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Mister ics <mister_ics@hotmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: on update restrict
Date: Tue, 14 Aug 2001 08:35:55 -0400 (EDT)
Message-ID: <200108141235.f7ECZtW01526@jupiter.us.greatbridge.com> (raw)
In-Reply-To: <F2139wPiyAphwFutJLt00006fb6@hotmail.com>

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
> costraint, the sql-server should not perform updates on the referenced rows.
> Here an example:
>
> testdb=>create table t1 (
>    id int primary key,
>    foo int);
> NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 't1_pkey' for
> table 't1'
> CREATE
>
> testdb=>create table t2 (
>    id int primary key,
>    ref int references t1(id) on update restrict);
> NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 't2_pkey' for
> table 't2'
> NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
> check(s)
> CREATE
>
> testdb=>insert into t1 values (1,3000);
> INSERT 19116 1
> testdb=>insert into t2 values (1,1);
> INSERT 19117 1
>
> testdb=> update t1 set foo=2900 where id=1;
> UPDATE 1    <--- for me is wrong, we have updated a row referenced by t2
> with ON UPDATE RESTRICT OPTION
>
> What do you think about ?

    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 id = 1;

    is the thing prevented in your above example.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (5+ messages)  latest in thread

Message-ID: <200108141235.f7ECZtW01526@jupiter.us.greatbridge.com>
Permalink:  ../200108141235.f7ECZtW01526@jupiter.us.greatbridge.com/
Also on:    postgresql.org/message-id/200108141235.f7ECZtW01526@jupiter.us.greatbridge.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: JanWieck@Yahoo.com, mister_ics@hotmail.com
  Subject: Re: on update restrict
  In-Reply-To: <200108141235.f7ECZtW01526@jupiter.us.greatbridge.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox