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

Re: Bug #619: Not possible to specify foreign key name

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: <dirk(dot)jacobs(at)tuple(dot)be>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug #619: Not possible to specify foreign key name
Date: 2002-03-15 16:25:32
Message-ID: 20020315082344.K50245-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, 15 Mar 2002 pgsql-bugs(at)postgresql(dot)org wrote:

> Dirk Jacobs (dirk(dot)jacobs(at)tuple(dot)be) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Not possible to specify foreign key name
>
> Long Description
> It is not possible to specify a foreign key name.
> Version 7.2 on redhat 7.2
>

Need more information, works for me:

create table b(a int constraint foo references a(a));
NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
CREATE
sszabo=# insert into b values(1);
ERROR:  foo referential integrity violation - key referenced from b not
found in a



In response to

pgsql-bugs by date

Next:From: Stephan SzaboDate: 2002-03-15 16:27:41
Subject: Re: Bug #620: create index ... (date_part('year', d)) fails
Previous:From: Peter EisentrautDate: 2002-03-15 16:21:27
Subject: Re: Bug #617: In SQL the tableowner is not allowed

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