Re: Stored Procedure and Trigger they puzzle me

From: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
To: "Lars Heidieker *EXTERN*" <lars(at)heidieker(dot)de>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Stored Procedure and Trigger they puzzle me
Date: 2006-12-18 09:26:50
Message-ID: 52EF20B2E3209443BC37736D00C3C1380BEC9934@EXADV1.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> The strange thing is:
> insert is OK (materialized path gets populated)
> update of parent column is OK old values get delete and new ones get
> inserted
> but if the exception handling of the unique_violation exception is
> removed an update on the id column fails, with
> an duplicate pkey violation an the self reference in the
> materialized
> path eg for the values (25, 25)
>
> It works OK with ignoring the exception but why is the exception
> thrown in the first place.

Could you provide a sequence of INSERT and UPDATE statements
that produce the problem you describe?

Yours,
Laurenz Albe

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2006-12-18 09:37:16 Re: Stored Procedure and Trigger they puzzle me
Previous Message Magnus Hagander 2006-12-18 09:18:53 Re: installing postgres on win Me...