-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 11:44, Albe Laurenz wrote:
Actually I just figured out, that is is not the trigger but the two
cascade on update triggers collide.
It happens also without the trigger:
lt=# UPDATE ltlocation SET id = 4 WHERE id = 18999;
ERRO
> Actually I just figured out, that is is not the trigger but the two
> cascade on update triggers collide.
> It happens also without the trigger:
>
> lt=# UPDATE ltlocation SET id = 4 WHERE id = 18999;
> ERROR: insert or update on table "ltlocationpath" violates foreign
> key constraint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 10:30, Lars Heidieker wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 08:56, Alban Hertroys wrote:
Not sure as I deleted them before, but currently I cant reproduce
it.
I just get the following now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 08:56, Alban Hertroys wrote:
Not sure as I deleted them before, but currently I cant reproduce it.
I just get the following now:
ERROR: insert or update on table "ltlocationpath" violates
foreign key
constraint "ltlocanceste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 08:45, Albe Laurenz wrote:
With your examples I can reproduce the error and explain what is going
on.
test=> select * from ltlocation;
id | name | description | parent | type
---+-+-
Lars Heidieker wrote:
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 colu
> CREATE TABLE ltlocation (
>"id" integer DEFAULT nextval('ltlocation_id_seq'::text) NOT NULL,
>name varchar(30) NOT NULL default '',
>"description" varchar(254) NOT NULL default '',
>"parent" int4,
>type int2 NOT NULL default '0',
>PRIMARY KEY (id)
> ) ;
>
> just to hold
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Dec 2006, at 09:37, Alban Hertroys wrote:
Lars Heidieker wrote:
Hi all,
I just started to write my first stored procedure in plpgsql and
installed a trigger for it.
The two Tables are:
CREATE TABLE ltlocation (
"id" integer DEFAULT next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Dec 2006, at 09:26, Albe Laurenz wrote:
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
Lars Heidieker wrote:
> Hi all,
>
> I just started to write my first stored procedure in plpgsql and
> installed a trigger for it.
>
> The two Tables are:
>
> CREATE TABLE ltlocation (
> "id" integer DEFAULT nextval('ltlocation_id_seq'::text) NOT NULL,
> name varchar(30) NOT NULL default '',
> 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 v
11 matches
Mail list logo
