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

Re: bug in information_schema?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Troels Arvin <troels(at)arvin(dot)dk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: bug in information_schema?
Date: 2004-11-27 18:20:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Troels Arvin <troels(at)arvin(dot)dk> writes:
> On Sat, 27 Nov 2004 14:24:40 +0000, Andrew - Supernews wrote:
>> something is assuming that constraint_name is unique within the schema,
>> which of course is not the case in the above example.

> The problem makes the INFORMATION_SCHEMA rather useless for some kinds of
> queries, like you have shown. However, I don't believe that schema-unique
> constraint names will be an option any time soon, due to backwards
> compatibility :-(

We have changed 8.0 to ensure that automatically-generated constraint
names are unique across a schema.  I doubt we will ever enforce that
against user-specified names, though.  If you want to use the
information schema to trace constraints, you'll have to impose that
discipline on yourself.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Dagoberto TorresDate: 2004-11-27 21:23:54
Subject: lo type
Previous:From: Tom LaneDate: 2004-11-27 17:55:09
Subject: Re: BUG #1329: Bug in IF-ELSEIF-ELSE construct

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