From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Truncation of char, varchar types |
Date: | 2001-04-10 17:05:51 |
Message-ID: | Pine.LNX.4.30.0104101904050.1403-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Nathan Myers writes:
> We have noticed here also that object (e.g. table) names get truncated
> in some places and not others. If you create a table with a long name,
> PG truncates the name and creates a table with the shorter name; but
> if you refer to the table by the same long name, PG reports an error.
This seems odd, because the truncation happens in the scanner. Care to
provide a test case?
> (Very long names may show up in machine- generated schemas.) Would
> patches for this, e.g. to refuse to create a table with an impossible
> name, be welcome?
Tom Lane is opposed to this, although a number of people seem to like it.
Sounds like a configuration option to me.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Butler | 2001-04-10 17:06:00 | Re: Indexes not used in 7.1RC4: Bug? |
Previous Message | Mike Mascari | 2001-04-10 16:41:59 | RE: Truncation of char, varchar types |