Re: issue about information_schema REFERENTIAL_CONSTRAINTS - Mailing list pgsql-bugs

From Tom Lane
Subject Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Date
Msg-id 22801.1283525905@sss.pgh.pa.us
Whole thread Raw
In response to Re: issue about information_schema REFERENTIAL_CONSTRAINTS  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: issue about information_schema REFERENTIAL_CONSTRAINTS  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: issue about information_schema REFERENTIAL_CONSTRAINTS  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-bugs
Fabien COELHO <coelho@cri.ensmp.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

pgsql-bugs by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Next
From: "Kevin Grittner"
Date:
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS