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: JanWieck@Yahoo.com
Cc: pgsql-sql@postgresql.org
Subject: Re: on update restrict
Date: Wed, 15 Aug 2001 10:02:11 -0400 (EDT)
Message-ID: <200108151402.f7FE2BW01192@jupiter.us.greatbridge.com> (raw)
In-Reply-To: <F91jkO22ZhCl8aii08N00007fba@hotmail.com>

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
> >
> >         UPDATE t1 SET id = 2 WHERE id = 1;
> >
> >     is the thing prevented in your above example.
> >
> >
> >Jan
> >
>
>
> Hi Jan,
>
> Thank you , i  understand now.
>
> Do you know a method to block the update of certain rows in a table not
> using the triggers ? I explain better:
> I have the needing to prevent the updating of a set of rows in a table. The
> first solution i can find is to use a boolean column (es. "Blocked") and
> rising a trigger on updating the table. The trigger checks if the row is
> updatable or not (checking the "Blocked" column).
> Is this the only (or better) way to do this ?

    Since  you  only want to suppress the operation in that case,
    it could be done with a rule too. But  I  think  the  cleaner
    solution  is  with  a  BEFORE  trigger  raising  an  ERROR or
    returning NULL to suppress the operation.

    And consider that you might want to be able  to  unblock  the
    row's  again.   In  that  case, the trigger is the only way I
    see, because you need  the  procedural  logic  to  check  the
    blocked true->false transition and let THAT change happen.


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)

Message-ID: <200108151402.f7FE2BW01192@jupiter.us.greatbridge.com>
Permalink:  ../200108151402.f7FE2BW01192@jupiter.us.greatbridge.com/
Also on:    postgresql.org/message-id/200108151402.f7FE2BW01192@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: <200108151402.f7FE2BW01192@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