From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | elein <elein(at)varlena(dot)com>, Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: join of array |
Date: | 2003-08-15 18:24:01 |
Message-ID: | 19830.1060971841@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> But I was disappointed that this doesn't:
> regression=# select ARRAY['{{1,2},{3,4}}'::int[],'{{5,6},{7,8}}'::int[]];
> ERROR: multidimensional ARRAY[] must be built from nested array expressions
Drat, I was assuming that that *would* work.
> Should I try to make the second and third cases work?
Could you look at how big a change it'd be, anyway? Offhand I think it
may just mean that the subscript-checking done in parse_expr.c needs to
be done at runtime instead. Remember parse_expr should only be
concerned about determining datatype, and for its purposes all arrays of
a given element type are the same --- subscript checking should happen
at runtime. (It seems likely that having an ndims field in ArrayExpr
is inappropriate.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory S. Williamson | 2003-08-15 18:26:57 | Re: importing db as text files |
Previous Message | elein | 2003-08-15 18:17:12 | Re: join of array |
From | Date | Subject | |
---|---|---|---|
Next Message | elein | 2003-08-15 18:32:13 | Re: Arrays and "goodness" in RDBMSs (was Re: join of array) |
Previous Message | elein | 2003-08-15 18:17:12 | Re: join of array |