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

Re: issue about information_schema REFERENTIAL_CONSTRAINTS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Date: 2010-09-03 14:58:25
Message-ID: 22801.1283525905@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-docs
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> Note that (2) fails for long names; you have to do something to
>> compress to NAMEDATALEN.

> Indeed.

> What if the type is changed to TEXT? It is just a view after all.
> How important is it to stick to "sql_identifier"?

It's a view defined by the SQL standard, and one of the properties
defined by the standard is the type of that column.

> Well, one must choose between to evil:

Yeah, exactly.  I think that the current tradeoff is just fine.
If you want SQL-standard behavior, pick SQL-standard constraint names,
and there you are.

			regards, tom lane

In response to

Responses

pgsql-docs by date

Next:From: Kevin GrittnerDate: 2010-09-03 15:14:35
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Previous:From: Fabien COELHODate: 2010-09-03 12:08:36
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS

pgsql-bugs by date

Next:From: Kevin GrittnerDate: 2010-09-03 15:14:35
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Previous:From: Fabien COELHODate: 2010-09-03 12:08:36
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS

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