On Sat, 2011-09-24 at 10:49 -0400, Bruce Momjian wrote:
I'll add that it would also cause a little confusion with inclusivity.
What if you do: '[5,2)'::int4range? Is that really '[2,5)' or '(2,5]'?
Reminder: BETWEEEN supports the SYMMETRIC keyword, so there is
a precedent for this.
And I
Reminder: BETWEEEN supports the SYMMETRIC keyword, so there is
a precedent for this.
And I don't see it as valuable enough to justify changing the
grammar.
I agree that we should leave symmetry until 9.3.
--Josh Berkus
--
Sent via pgsql-hackers mailing list
Jeff Davis wrote:
On Tue, 2011-09-13 at 12:34 -0400, Christopher Browne wrote:
select int4range(5,2);
ERROR: range lower bound must be less than or equal to range upper bound
Of course, I won't argue this is a bug, but I was wondering if it
wouldn't be handy to allow a
Hi,
Just a thought:
select int4range(5,2);
ERROR: range lower bound must be less than or equal to range upper bound
Of course, I won't argue this is a bug, but I was wondering if it wouldn't be
handy to allow a
'symmetric' mode in range construction, where, if the first of the pair is
higher
On Tue, Sep 13, 2011 at 12:08 PM, Erik Rijkers e...@xs4all.nl wrote:
Just a thought:
select int4range(5,2);
ERROR: range lower bound must be less than or equal to range upper bound
Of course, I won't argue this is a bug, but I was wondering if it wouldn't be
handy to allow a
'symmetric'
On Tue, 2011-09-13 at 12:34 -0400, Christopher Browne wrote:
select int4range(5,2);
ERROR: range lower bound must be less than or equal to range upper bound
Of course, I won't argue this is a bug, but I was wondering if it wouldn't
be handy to allow a
'symmetric' mode in range
