Re: Range Types - typo + NULL string constructor - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Range Types - typo + NULL string constructor
Date
Msg-id CA+TgmobhTRaDWw6BrKnkUySkP3Q2seoHqWWyQ3hmP6ruy1zXfw@mail.gmail.com
Whole thread Raw
In response to Re: Range Types - typo + NULL string constructor  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
On Wed, Sep 21, 2011 at 8:41 AM, Florian Pflug <fgp@phlo.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


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Range Types - typo + NULL string constructor
Next
From: Greg Stark
Date:
Subject: Re: Inlining comparators as a performance optimisation