From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: array type name mangling |
Date: | 2007-05-05 15:13:33 |
Message-ID: | 19607.1178378013@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> In connection with completing David Fetter's array of composites patch,
> I am looking at doing some better name mangling for array types as
> recently discussed. What I'm thinking of is prepending one or more
> underscores to the type name up to some limit (NAMEDATALEN / 2 ?) and if
> necessary truncating the result, and then looking to see if there is a
> name clash. That would, I hope, enable us to get rid of all the places
> where we require names to be no more than NAMEDATALEN - 2 chars. Does
> that seem like a reasonable approach? Will it break anything, i.e., is
> there somewhere that has assumes the array type for foo will be called
> _foo rather than ___foo ?
makeArrayTypeName and users thereof. Or are you going to extend pg_type
to have a direct link?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2007-05-05 15:15:35 | Re: Patch Status in the wiki |
Previous Message | Andrew Dunstan | 2007-05-05 15:08:10 | Re: array type name mangling |