Re: [PATCH] SQL function to report log message

Поиск
Список
Период
Сортировка
От dinesh kumar
Тема Re: [PATCH] SQL function to report log message
Дата
Msg-id CALnrH7pOLR2Hpt0aGYiffZEFZmUprB=aDqDQ=jbewf_4HdNL0A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] SQL function to report log message  (Kevin Grittner <kgrittn@ymail.com>)
Список pgsql-hackers
On Mon, Nov 16, 2015 at 3:58 PM, Kevin Grittner <kgrittn@ymail.com> wrote:
On Sunday, November 15, 2015 8:51 PM, Craig Ringer <craig@2ndquadrant.com> wrote:

> I'd prefer to omit fields if explicitly assigned to NULL. You can
> always use coalesce if you want the string 'NULL'; I agree with
> others here that the vast majority of users will want the field
> just omitted.

+1

Unfortunately those writing the SQL standard chose to have a single
flag (NULL) to indicate either "unknown" or "not applicable".  That
causes problems where it's not clear which way the value should be
interpreted, but in this case it seems pretty clear that someone
passing a NULL parameter for hint to a function like this doesn't
mean "there is likely to be a valid value for hint, but I don't
know what it is" -- they mean there is no available hint, so please
don't show one.  Any other behavior seems rather silly.

Thanks Kevin/Craig for your comments.

 
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



--

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Proposal: "Causal reads" mode for load balancing reads without stale data
Следующее
От: Kevin Grittner
Дата:
Сообщение: Re: Question concerning XTM (eXtensible Transaction Manager API)