Re: SQL access to database attributes
| От | Pavel Stehule |
|---|---|
| Тема | Re: SQL access to database attributes |
| Дата | |
| Msg-id | CAFj8pRD2rTkwiTWY6ZxfQURssN-cUV4y+eU8sbarC0gfXmmshQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: SQL access to database attributes (Vik Fearing <vik.fearing@dalibo.com>) |
| Ответы |
Re: SQL access to database attributes
|
| Список | pgsql-hackers |
2014-06-23 18:39 GMT+02:00 Vik Fearing <vik.fearing@dalibo.com>:
On 06/23/2014 06:21 PM, Robert Haas wrote:Why do we want to document syntax that should eventually be deprecated?
> On Sun, Jun 22, 2014 at 2:59 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> I found only one problem - first patch introduce a new property
>> CONNECTION_LIMIT and replace previously used "CONNECTION LIMIT" in
>> documentation. But "CONNECTION LIMIT" is still supported, but it is not
>> documented. So for some readers it can look like breaking compatibility, but
>> it is false. This should be documented better.
>
> Yeah, I think the old syntax should be documented also.
It is fair to our users. It can be deprecated, ok, we can write in doc - this feature will be deprecated in next three years. Don't use it, but this should be documentated.
Pavel
Exactly. We're still carrying around baggage from 7.2!
> See, e.g., what we do for COPY.
Backward compatibility: yes.
Backward documentation: no.
--
Vik
В списке pgsql-hackers по дате отправления: