| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "deinspanjer(at)gmail(dot)com" <deinspanjer(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset |
| Date: | 2018-02-25 02:11:40 |
| Message-ID: | CAKFQuwYhRsU_Qw4ird9YwgjQNxxX4+1Z0YDbRRGH_CENmOBDfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Saturday, February 24, 2018, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15085
> Logged by: Daniel Einspanjer
> Email address: deinspanjer(at)gmail(dot)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.
https://www.postgresql.org/docs/9.6/static/sql-createdomain.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-25 03:35:06 | Re: BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset |
| Previous Message | PG Bug reporting form | 2018-02-25 01:08:17 | BUG #15085: Domain "not null" constraint doesn't detect a null returned from a resultset |