Re: Document NULL
| От | Marcos Pegoraro |
|---|---|
| Тема | Re: Document NULL |
| Дата | |
| Msg-id | CAB-JLwbjzGL-Jtb-AuTrgBkVWKH8LUXDu3wxkLyOLHXUH4UYmg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Document NULL (Álvaro Herrera <alvherre@kurilemu.de>) |
| Список | pgsql-hackers |
Em ter., 11 de nov. de 2025 às 12:34, Álvaro Herrera <alvherre@kurilemu.de> escreveu:
I have rebased this; here's v9. I haven't reviewed it in depth, but
intend to give it a read and get it pushed sometime in the
not-too-distant future, so if anybody wants to review it some more, it'd
be appreciated.
- Reading this document I see that he uses "the empty string" but DOCs uses more "an empty string".
Then a few minutes ago I sent a patch [1] to use "an empty string" instead of "the empty string".
If that patch is accepted then this could be done here too.
- I think using several commands and their results in a <programlisting> is difficult to read,
mainly because some commands result on 2 or more lines, some an empty line,
so it is difficult to see what command generated what result. Maybe separate them into 2 blocks, maybe.
<programlisting>
-- The transaction markers are left here to emphasize the rollback behavior.
SHOW example.string;
BEGIN;
SELECT set_config('example.string', NULL, true);
SELECT current_setting('example.string') IS NULL AS "Setting Is Null";
ROLLBACK;
SHOW example.string;
RESET example.string;
SHOW example.string;
</programlisting>
SHOW example.string;
BEGIN;
SELECT set_config('example.string', NULL, true);
SELECT current_setting('example.string') IS NULL AS "Setting Is Null";
ROLLBACK;
SHOW example.string;
RESET example.string;
SHOW example.string;
</programlisting>
regards
Marcos
В списке pgsql-hackers по дате отправления: