From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Kris Jurka <books(at)ejurka(dot)com> |
Subject: | Re: [PATCHES] [BUGS] casting strings to multidimensional arrays yields |
Date: | 2004-08-07 18:29:07 |
Message-ID: | 41151F73.4030405@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers pgsql-patches |
Tom Lane wrote:
> I'm not sure that we had such an agreement, but in any case we've got
> to understand how to distinguish empty-string from NULL.
>
I realized that in my followup post regarding nested arrays. In any
case, since will not 8.0 support either NULL elements nor nested arrays,
can we agree that '{{},{}}' and similar is not allowed? If someone
really wants '{{""},{""}}', they will still be able to specify it in
that precise way.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-08-09 01:56:14 | 8.0: Absolute path required for INITDB? |
Previous Message | Tom Lane | 2004-08-07 16:51:21 | Re: BUG #1207: retrieve error |
From | Date | Subject | |
---|---|---|---|
Next Message | matt nations | 2004-08-07 20:32:01 | Re: PostgreSQL as an application server |
Previous Message | Bruce Momjian | 2004-08-07 18:07:39 | Re: PITR - recovery to a particular transaction |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2004-08-07 21:43:04 | Re: UNICODE characters above 0x10000 |
Previous Message | Tom Lane | 2004-08-07 16:53:49 | Re: PITR on Win32 - Archive and Restore Command Strings |