Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
makeArrayTypeName and users thereof. Or are you going to extend pg_type
to have a direct link?
I am going to change makeArrayTypeName() to do the mangling. Its users
will need to pass in a namespa
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Actually, looking back in the email history I see Tom suggested this,
> which I'll try instead:
>> prepend _, truncate to less than 64 bytes if necessary,
>> then substitute numbers at the end if needed to get something unique.
Your idea of multiple
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> makeArrayTypeName and users thereof. Or are you going to extend pg_type
>> to have a direct link?
> I am going to change makeArrayTypeName() to do the mangling. Its users
> will need to pass in a namespace as well as a typename so i
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> 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
Andrew Dunstan <[EMAIL PROTECTED]> 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
I wrote:
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 ne
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 tru
