Re: BUG #17464: Domain type. If the value field(CREATE DOMAIN) is set to null, errors cannot be intercepted.

On Tue, Apr 12, 2022 at 7:16 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 17464
> Logged by: Domain type. If the value field(CREATE DOMAIN) is set
> to null, errors cannot
> be intercepted.
> Email address: dafoer_x(at)163(dot)com
> PostgreSQL version: 13.2
> Operating system: centos7.6 x86
> Description:
>
> Domain type. If the value field(CREATE DOMAIN) is set to null, errors
> cannot
> be intercepted.
> Because texteq cannot accept null input parameters,
> op->d.domainCheck.checknull is set to the wrong value .
>

I'm not really following, and don't have time to investigate this right
now, but:

CREATE DOMAIN xb AS TEXT CHECK
> (
> VALUE = '男'
> OR VALUE ='女'
> OR VALUE = null
> );
>
>
"VALUES = null" is simply wrong. That isn't how one checks for null. Use
"IS NULL". If that restores the correct behavior I'm unsure what we'd be
willing to do to behave differently in the presence of the improper null
test form.

David J.