Re: [HACKERS] A notice for too long names - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] A notice for too long names
Date
Msg-id 21095.948383705@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] A notice for too long names  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
Responses Re: [HACKERS] A notice for too long names
List pgsql-hackers
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> Wouldn't it be fair if a notice was generated if you attempt to create
>> and/or reference a name that's longer than NAMEDATALEN.

> Would it be better to throw an elog(ERROR)?

Definitely NOT.  Rejecting long identifiers went out with Dartmouth Basic.

The only reason to worry at all is if someone uses two identifiers that
are the same for the first NAMEDATALEN characters --- but if so, he'll
get an error about duplicate column or duplicate table name.  I see no
real reason to change the current behavior...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] timezone problem?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] COPY problems with psql / libpq