| From: | Zhihong Yu <zyu(at)yugabyte(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UNIQUE null treatment option |
| Date: | 2021-12-29 23:27:57 |
| Message-ID: | CALNJ-vQNtvaOxmZsvWYTSh5oApUHtMaoWEwXmgNwjvy=madG_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
bool isunique;
+ bool nulls_not_distinct;
} BTSpool;
Looking at the other fields in BTSpool, there is no underscore in field
name.
I think the new field can be named nullsdistinct. This way, the
double negative is avoided.
Similar comment for new fields in BTShared and BTLeader.
And the naming would be consistent with information_schema.sql where
nulls_distinct is used:
+ CAST('YES' AS yes_or_no) AS enforced,
+ CAST(NULL AS yes_or_no) AS nulls_distinct
Cheers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-12-30 00:15:08 | Re: Column Filtering in Logical Replication |
| Previous Message | Joel Jacobson | 2021-12-29 23:11:26 | SELECT documentation |