Hi hackers
Wouldn't it be better to raise an error when identifiers are too long,
rather than accepting but truncating them? I'm not aware of any other
database that does this. If you're using oversized identifiers you
could finish up using more than one way to refer to the same database
Thomas Munro writes:
> Wouldn't it be better to raise an error when identifiers are too long,
> rather than accepting but truncating them?
I wouldn't think so.
> I'm not aware of any other database that does this.
It's standard practice in most programming
On 14/01/16 13:05, Tom Lane wrote:
Thomas Munro writes:
Wouldn't it be better to raise an error when identifiers are too long,
rather than accepting but truncating them?
I wouldn't think so.
I'm not aware of any other database that does this.
It's standard