pgsql: Return NULL instead of throwing error when desired bound is not

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Return NULL instead of throwing error when desired bound is not
Дата
Msg-id E1RQ3Eu-0007xX-UA@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Return NULL instead of throwing error when desired bound is not available.

Change range_lower and range_upper to return NULL rather than throwing an
error when the input range is empty or the relevant bound is infinite.  Per
discussion, throwing an error seems likely to be unduly hard to work with.
Also, this is more consistent with the behavior of the constructors, which
treat NULL as meaning an infinite bound.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/4f9e33063cea270166fba12d89fe49876f814398

Modified Files
--------------
doc/src/sgml/func.sgml             |    8 ++++++++
src/backend/utils/adt/rangetypes.c |   22 ++++++----------------
2 files changed, 14 insertions(+), 16 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Return FALSE instead of throwing error for comparisons with empt
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Update oidjoins regression test to match git HEAD.