| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should array_length() Return NULL |
| Date: | 2013-03-17 04:31:52 |
| Message-ID: | CADxJZo30YCHBeoLyzH_BjUrVDr_+gcNx-pBw+R9yqTnJghoCQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 March 2013 06:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> What I'm concerned about here is whether these expressions shouldn't
> be yielding different data values:
>
>
> Right now, if we did make them produce what they appear to mean, the
> array I/O functions would have a problem with representing the results:
>
> So I think we'd need to fix that before we could go very far in this
> direction.
I agree. I am starting to work on that very thing.
I noticed that there are a whole bunch of errmsgs in ArrayCount and
ReadArrayStr that just say "malformed array literal" with no detail
message at all. Not very helpful. I'm tempted to improve that on my
way past.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-17 04:41:43 | Re: Should array_length() Return NULL |
| Previous Message | Tom Lane | 2013-03-17 03:53:50 | Re: Strange Windows problem, lock_timeout test request |