| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: array type name mangling |
| Date: | 2007-05-05 19:05:16 |
| Message-ID: | 463CD56C.8090707@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> 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 it can do the
>> checking.
>>
>
> You missed the point: there is a need to find the array type associated
> with an existing element type, not only the other way round. See
> LookupTypeName() and get_array_type().
>
>
>
OK, in that case I think we should extend pg_type with a direct link,
don't you?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-05-05 20:00:05 | Re: iterating over relation's attributes |
| Previous Message | Tom Lane | 2007-05-05 18:51:47 | Re: array type name mangling |