| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types - typo + NULL string constructor |
| Date: | 2011-09-21 12:47:00 |
| Message-ID: | CA+TgmobhTRaDWw6BrKnkUySkP3Q2seoHqWWyQ3hmP6ruy1zXfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 21, 2011 at 8:41 AM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
>> Boy, that seems really weird to me. If you're going to do it, it
>> ought to be case-insensitive, but I think detecting the case only for
>> the purpose of rejecting it is probably a mistake. I mean, if
>> (nubile, nutty) is OK, then (nubile, null) and (null, nutty) don't
>> really seem like they ought to be any different.
>
> But that's exactly how arrays behave too. '{null,nutty}' is interpreted
> as ARRAY[NULL,'nutty'] while '{nubile,nutty}' is interpreted as
> ARRAY['nubile','nutty'].
Oh. Well, never mind then.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2011-09-21 12:47:46 | Re: Inlining comparators as a performance optimisation |
| Previous Message | Florian Pflug | 2011-09-21 12:41:15 | Re: Range Types - typo + NULL string constructor |