On Mon, Sep 19, 2011 at 1:51 AM, Jeff Davis <pg...@j-davis.com> wrote: >> select '[ 2 , NULL )'::int4range; >> ERROR: NULL range boundaries are not supported >> LINE 1: select '[ 2 , NULL )'::int4range; > > I think this might require more opinions. There is a trade-off here > between convenience and confusion: accepting NULL is convenient in the > constructors, because it avoids the need to have extra constructors just > for unbounded ranges; but could lead to confusion between NULL and INF > (which are not the same).
I agree with this line of reasoning. I think we will be making pain for ourselves if we need to invent a bunch more constructors just to have a way of indicating an unbounded range, but OTOH I don't see any compelling reason why the type input function needs to accept N-U-L-L. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
