|From:||"Thomas G(dot) Lockhart" <Thomas(dot)Lockhart(at)jpl(dot)nasa(dot)gov>|
|Cc:||Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, martin(at)biochemistry(dot)ucl(dot)ac(dot)uk|
|Subject:||Re: [HACKERS] Array bug is still there....|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Andrew Martin wrote:
> Just run the regression tests on 6.1 and as I suspected the array bug
> is still there. The regression test passes because the expected output
> has been fixed to the *wrong* output.
OK, I think I understand the current array behavior, which is apparently
different than the behavior for v1.0x.
Postgres v6.1 allows one to specify a dimensionality for an array object
when declaring that object/column. However, that specification is not
used when decoding a field. Instead, the dimensionality is deduced from
the input string itself. The dimensionality is stored with each field,
and is used to encode the array on output. So, one is currently allowed
to mix array dimensions within a column, but Postgres seems to keep that
all straight for input and output.
Is this the behavior that we want? Just because it is different from
previous behavior doesn't mean that it is undesirable. However, when
mixing dimensionality within the same column it must be more difficult
to figure out how to do comparison and other operations on arrays.
If we are to enforce dimensionality within columns, then I need to
figure out how to get that information from the table declaration when
decoding fields. Bruce, do you know where to look for that kind of code?
Anyone have an idea on how much this code has changed over the last
|Next Message||Marc G. Fournier||1998-01-04 05:47:02||setting up mhonarc one list at a time|
|Previous Message||infotechsys||1996-05-30 22:58:15||http://www.postgresql.org/devel-mlists.shtml|