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 -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers