Re: Range Types: << >> -|- ops vs empty range
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Erik Rijkers <er@xs4all.nl>
Cc: Jeff Davis <pgsql@j-davis.com>, pgsql-hackers@postgresql.org
Date: 2011-03-11T13:37:08Z
Lists: pgsql-hackers
Where are we on this? --------------------------------------------------------------------------- Erik Rijkers wrote: > On Wed, February 9, 2011 09:35, Jeff Davis wrote: > > Updated patch. > > > > The operators << >> and -|- have the following behavior with empty ranges: > > testdb=# select '-'::int4range << range(200,300); > ERROR: empty range > testdb=# select '-'::int4range >> range(200,300); > ERROR: empty range > testdb=# select '-'::int4range -|- range(200,300); > ERROR: empty range > > I'm not sure if that is deliberate behavior, but they seem > almost bugs to me. > > Wouldn't it be better (and more practical) if these would > return false (or perhaps NULL, for 'unknown') ? > > (the same goes for all the other range types, btw.) > > > Erik Rijkers > > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +