From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Some array semantics issues |
Date: | 2005-11-18 01:16:44 |
Message-ID: | 29486.1132276604@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Tom Lane wrote:
>> If we can't use an OID to identify a data type
>> completely, we're going to have lots of problems.
> You only really need two pieces of information to uniquely identify an
> array data type -- the OID of the (leaf-node) scalar elements, and the
> fact that what you have is an array.
Yes, but replacing one piece of data (type OID) with two (type OID plus
array flag bit) is going to be notationally horrible. What's more it
will force knowledge about the existence of array types into a lot of
places that don't have to care right now. For something that is
ultimately just a flange on the side of SQL, that doesn't seem like a
good tradeoff.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-18 01:41:51 | Anyone want to fix plperl for null array elements? |
Previous Message | Alvaro Herrera | 2005-11-18 00:57:38 | Re: CLUSTER and clustered indices |