The following bug has been logged online:
Bug reference: 2927
Logged by: Jaume Catarineu
Email address: jaume(at)nobainfo(dot)net
PostgreSQL version: 8.2.1
Operating system: Linux srvca01 126.96.36.199-20a-smp #1 SMP Wed Mar 23
21:52:37 UTC 2005 i686 i686 i386 GNU/Linux
Description: Trigger execution hides foreign key error
When a table has a foreign key field if you insert values that violate that
check an error appears:
ERROR: insert or update on table "m_tran" violates foreign key constraint
That's ok, but when a INSERT trigger is added to that table, the precedent
insert order productes the following output:
INSERT 0 0
And no error appears anywhere: neither in the log nor the psql console.
Shouldn't PostgreSQL inform someway why it's not going to insert that row?
It seems like the correct trigger execution was hidding the previous
incorrect foreign key check. Is that way?
pgsql-bugs by date
|Next:||From: Jeff Trout||Date: 2007-01-24 15:15:03|
|Subject: Function returns wrong data after datatype change|
|Previous:||From: Mandeep||Date: 2007-01-24 09:05:47|
|Subject: BUG #2926: E_OUTOFMEMORY|