Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE
Дата
Msg-id CA+TgmoboWs6UPvkm5RENmQ9BNQxVAr6uYOHdR+FwvO1KNj13vw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On Fri, Jan 6, 2017 at 7:29 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 1/3/17 11:52 PM, Ashutosh Bapat wrote:
>> We will need to make CURRENT_DATABASE a reserved keyword. But I like
>> this idea more than COMMENT ON CURRENT DATABASE.
>
> We already have the reserved key word CURRENT_CATALOG, which is the
> standard spelling.  But I wouldn't be bothered if we made
> CURRENT_DATABASE somewhat reserved as well.

Maybe I'm just lacking in imagination, but what's the argument against
spelling it CURRENT DATABASE?  AFAICS, that doesn't require reserving
anything new at all, and it also looks more SQL-ish to me.  SQL
generally tries to emulate English, and I don't normally
speak_hyphenated_words.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] _hash_addovflpage has a bug
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] increasing the default WAL segment size