On Sun, 2024-03-24 at 17:32 +0100, Thiemo Kellner wrote:
> > The reason it doesn't give you a warning is that by the time it would
> > be in a position to, it's forgotten that you explicitly said NULL.
>
> How can that be forgotten? This information ends up in the data
> catalogue eventually!
It *is* stored in the catalog.
But if you add a primary key, that is tantamount to saying
ALTER TABLE tab ALTER col SET NOT NULL;
So it overrides the definition you made before.
Or would you want the above statement to cause an error just
because somebody had defined the column nullable before?
Perhaps you'd want that, but you are one of the few who do.
You'll have to get used to the way it is.
Yours,
Laurenz Albe