Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] unfortunately...

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Vadim Mikheev <vadim(at)krs(dot)ru>
Cc: hackers(at)postgreSQL(dot)org, darcy(at)druid(dot)net
Subject: Re: [HACKERS] unfortunately...
Date: 1998-09-25 11:18:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, 25 Sep 1998, Vadim Mikheev wrote:

> I don't like implementation of referential integrity constraints 
> in contrib/spi/refint.* and implementation of ... unique indices:
> backend checks constraints when tuple is changed.
> Oracle checks constraints after entire _statement_ is done.
> Do you remember this:
> vac=> create table x (a int unique);
> NOTICE:  CREATE TABLE/UNIQUE will create implicit index x_a_key for table x
> vac=> insert into x values (1);
> INSERT 143852 1
> vac=> insert into x values (2);
> INSERT 143853 1
> vac=> update x set a = a + 1;
> ERROR:  Cannot insert a duplicate key into a unique index
> This is simplest case. Keeping in mind triggers
> I would like to see Oracle behaviour some day and so
> I decided to do not implement FOREIGN keys in 6.4 -:((

	Sounds reasonable to me...all things considered, I think that v6.4
has turned out, once more, to be one giant leap forward :)

> Sorry.

	Don't be...I think if Bruce had his way, we'd be funding a cloning
project just so that we could get a dozen of you :)  Its nice to be
reminded once in a while that you are "only human" *grin*

In response to

pgsql-hackers by date

Next:From: Thomas G. LockhartDate: 1998-09-25 14:40:13
Subject: Re: [HACKERS] Re: Problem dropping databases
Previous:From: Jan WieckDate: 1998-09-25 09:33:04
Subject: Re: [HACKERS] crash on new system views

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group