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

Re: fkey + primary key does not work in current

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: fkey + primary key does not work in current
Date: 2000-09-15 17:02:59
Message-ID: Pine.BSF.4.10.10009150956300.33438-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 15 Sep 2000, Tatsuo Ishii wrote:

> It seems that foreign key does not work in current, if specified with
> primary key definition. Take a look at following example(works in
> 7.0.2.):
> 
> test=# CREATE TABLE PKTABLE ( ptest1 int, ptest2 int, ptest3 int, ptest4 text, PRIMARY KEY(ptest1, ptest2, ptest3) );
> NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable'
> CREATE
> test=# CREATE TABLE FKTABLE ( ftest1 int, ftest2 int, ftest3 int, ftest4 int, primary key (ftest1,ftest2,ftest3,ftest4),  CONSTRAINT constrname3 FOREIGN KEY(ftest1, ftest2, ftest3) REFERENCES PKTABLE);
> NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'fktable_pkey' for table 'fktable'
> NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
> ERROR:  columns referenced in foreign key constraint not found.

Hmm, that's very strange.  I wonder which columns it think didn't exist.
It shouldn't be checking the pktable in that case, which would imply
it doesn't believe the existance of ftest1,ftest2,ftest3.  Probably
a stupid mistake on my part.  As soon as I clear off space to compile
current, I'll look.


In response to

Responses

pgsql-hackers by date

Next:From: Eje GustafssonDate: 2000-09-15 17:11:05
Subject: Expired records ?
Previous:From: Tom LaneDate: 2000-09-15 14:24:30
Subject: Re: Cannot compile

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