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

From Jeff Davis
Subject Re: Range Types - typo + NULL string constructor
Date
Msg-id 1316671282.7281.228.camel@jdavis
Whole thread Raw
In response to Re: Range Types - typo + NULL string constructor  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
On Thu, 2011-09-22 at 02:31 +0200, Florian Pflug wrote:
> My personal favourite would be '0', since it resembles the symbol used
> for empty sets in mathematics, and we already decided to use mathematical
> notation for ranges.
> 
> If we're concerned that most of our users won't get that, then 'empty'
> would be a viable alternative I think.
> 
> From a consistency POV it'd make sense to use a bracket-based syntax
> also for empty ranges. But the only available options would be '()' and '[]',
> which are too easily confused with '(,)' and '[,]' (which we already
> decided should represent the full range).

Yes, I think () is too close to (,).

Brainstorming so far:0       : simple, looks like the empty set symbolempty   : simple<empty> : a little more obvious
thatit's special<>      : visually looks empty-       : also looks empty{}      : mathematical notation, but doesn't
quitefit ranges
 

I don't have a strong opinion. I'd be OK with any of those.

Regards,Jeff Davis




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: EXPLAIN and nfiltered, take two
Next
From: Heikki Linnakangas
Date:
Subject: Re: EXPLAIN and nfiltered, take two