Re: Catalog domain not-null constraints

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>
Subject: Re: Catalog domain not-null constraints
Date: 2024-03-22 01:12:48
Message-ID: ee635b6f-3911-41c0-aff7-bb268e01e92e@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/22/24 01:46, Tom Lane wrote:
> Vik Fearing <vik(at)postgresfriends(dot)org> writes:
>> Anyway, I will bring this up with the committee and report back. My
>> proposed solution will be for CAST to check domain constraints even if
>> the input is NULL.
>
> Please do not claim that that is the position of the Postgres project.

Everything that I do on the SQL Committee is in my own name.

I do not speak for either PostgreSQL or for EDB (my employer), even
though my opinions are of course often influenced by some combination of
both.
--
Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-03-22 01:52:51 Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs
Previous Message Nathan Bossart 2024-03-22 01:03:32 Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs