From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Nathan Boley <npboley(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Scott Bailey <artacus(at)comcast(dot)net>, hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Range types |
Date: | 2009-12-14 18:22:03 |
Message-ID: | 1260814923.15987.411.camel@jdavis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2009-12-14 at 10:00 -0800, Nathan Boley wrote:
> IMHO the first question is whether, for integers, [1,2] UNION [3,5]
> should be equal to [1,5]. In math this is certainly true, and defining
> 'next' seems like a reasonable way to establish this in postgres.
[ you say "yes" ]
Agreed.
> The next question is whether, for floats, [1,3-FLT_EPSILON] UNION
> [3,5] should be [1,5].
[ you say "no" ]
I think this should be true, because all floats between 1 and 5 are
contained. I don't feel too strongly about this, so I would not complain
if floats were treated as continuous.
> And the next question is whether, for numeric(6,2), [1,2.99] UNION
> [3,5] should be [1,5].
[ you say "yes" ]
I almost agree. Unfortunately, typmod isn't really a part of the type,
it just affects input/output. So, we can't really use it that way -- as
Tom points out, typmod is not passed along to functions that take the
value.
But if it were a part of the type, then I would certainly agree.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-12-14 18:31:30 | Re: Range types |
Previous Message | Tom Lane | 2009-12-14 18:21:22 | Re: Range types |