Use a trigger and if the trigger fails then it should rollback everything
that you had done.
Triggers can be fired per row instead of the whole table once the update
is completed
Darren Ferguson
On Thu, 31 Jan 2002, Ben-Nes Michael wrote:
> > > Is there a way to do UNIQUE check after the whole table got updated ?
> > > If not, any ideas to walk around the problem ?
> > The closest thing I could think of would be a constraint trigger that did
> > a uniqueness check but that'll probably be somewhat slower (a trigger that
> > looks for something like: select lft from areas group by lft having
> > count(*)>1;)
>
> How can I rollback in a function ?
> I mean after update has been done, I do some checking in the Function and
> then decide that I want to quit and rollback all what inserted/updated in
> the start of the function ?
>
> Also if I attach trigger that check column uniqueness to an update will it
> check it per updated row or at the end of the action after all the table got
> updated ?
>
> Cheer
>
> --------------------------
> Canaan Surfing Ltd.
> Internet Service Providers
> Ben-Nes Michael - Manager
> Tel: 972-4-6991122
> http://sites.canaan.co.il
> --------------------------
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
