| From: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Is this a buggy behavior? |
| Date: | 2024-03-24 18:09:12 |
| Message-ID: | ff834a59-7c85-4d61-be76-7f31233623cc@gelassene-pferde.biz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 24.03.2024 um 17:43 schrieb Christophe Pettus:
> The situation is much more like the customer saying, "I understand that the standard paint for this car is red, but I wish it painted blue instead."
Not in the least. Declaring the column to be NULL is explicitly
requesting the car be blue. And declaring, in the same statement, there
be a pk on that column is implicitly requesting the car be red.
> Again, you can argue that PostgreSQL should remember that you explicitly asked for a NULL and generate a warning in that case, but that's not a trivial amount of work, since right now, that NULL is thrown away very early in statement processing.
Only, if PG is not aware of being in the process of creating a table.
Well, I do not feel, I can make myself understood.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thiemo Kellner | 2024-03-24 18:12:58 | Empty materialized view |
| Previous Message | Christophe Pettus | 2024-03-24 16:43:58 | Re: Is this a buggy behavior? |