| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(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-10-02 16:01:10 |
| Message-ID: | 1317571270.1724.38.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2011-10-02 at 11:32 +0200, Florian Pflug wrote:
> Looking at the patch, I noticed that it's possible to specify the default
> boundaries ([], [), (] or ()) per individual float type with the
> DEFAULT_FLAGS clause of CREATE TYPE .. AS RANGE. I wonder if that doesn't
> do more harm then good - it makes it impossible to deduce the meaning of
> e.g. numericrange(1.0, 2.0) without looking up the definition of numericrange.
>
> I suggest we pick one set of default boundaries, ideally '[)' since that
> is what all the built-in canonization functions produce, and stick with it.
That sounds reasonable to me. Unless someone objects, I'll make the
change in the next patch.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2011-10-02 17:16:33 | Re: [v9.2] Fix Leaky View Problem |
| Previous Message | Noah Misch | 2011-10-02 12:50:09 | Re: pg_cancel_backend by non-superuser |