Re: BUG #15085: Domain "not null" constraint doesn't detect a nullreturned from a resultset - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15085: Domain "not null" constraint doesn't detect a nullreturned from a resultset
Date
Msg-id CAKFQuwYhRsU_Qw4ird9YwgjQNxxX4+1Z0YDbRRGH_CENmOBDfg@mail.gmail.com
Whole thread Raw
In response to BUG #15085: Domain "not null" constraint doesn't detect a nullreturned from a resultset  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Saturday, February 24, 2018, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15085
Logged by:          Daniel Einspanjer
Email address:      deinspanjer@gmail.com
PostgreSQL version: 9.6.7
Operating system:   Linux
Description:

I was trying to create two domains, one that allowed nulls, and another that
built on it that didn't allow nulls.  After some testing, I came across this
unusual behavior that I believe might be a bug.
I did check the TODO and tried to do some web searches (hard keywords to
work with here) but I didn't find any reports about this.

This appears to fall within the exceptions for not null noted in the documentation for create domain.


David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15085: Domain "not null" constraint doesn't detect a nullreturned from a resultset
Next
From: Tom Lane
Date:
Subject: Re: BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset