Horton

RE: POSTGRES BUG - FIX IT PLEASE

Vadim Mikheev <vmikheev@sectorbase.com>

View thread
From: "Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
To: "'Peter Eisentraut'" <peter_e@gmx.net>, Sergey Mavrinsky <mavr@solvo.ru>
Cc: pgsql-bugs@postgresql.org, "'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgresql.org>
Date: 2000-10-10T20:07:13Z
Lists: pgsql-bugs, pgsql-hackers 
> > create table t1
> > (
> >         f1 integer,
> >         f2 integer
> > );
> > 
> > create table t2
> > (
> >         f1 integer references t1(f1),
> >         f2 integer
> > );
> 
> > begin transaction;
> > insert into t1(f1,f2) values(1,1);
> > delete from t1 where f1=1;
> 
> > ERROR:  triggered data change violation on relation "t1"
> 
> You cannot change data twice within a transaction if there's a RI
> constraint on the table.  This is per SQL, nothing we can do about it.
                            ^^^^^^^^^^^^^^^
Is it true?! *Any reasons* for this? DELETE doesn't break integrity rules.
Just tested it in Oracle - deletion is allowed!
But yes, I know that Oracle doesn't always follow standards -:)
Can someone test it under Informix, others?

Vadim