Re: misleading lang_name case in CREATE FUNCTION doc.

Поиск
Список
Период
Сортировка
От Marc Mamin
Тема Re: misleading lang_name case in CREATE FUNCTION doc.
Дата
Msg-id B6F6FD62F2624C4C9916AC0175D56D880CE4740C@jenmbs01.ad.intershop.net
обсуждение исходный текст
Ответ на Re: misleading lang_name case in CREATE FUNCTION doc.  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: misleading lang_name case in CREATE FUNCTION doc.  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-docs

> From: Peter Eisentraut [mailto:peter_e@gmx.net]
> Sent: Mittwoch, 13. November 2013 12:56


> On Fri, 2013-10-11 at 08:37 +0000, Marc Mamin wrote:
> > Hi,
> > you might want to lowercase the language names in order to be
> > compatible with the case restriction introduced in  9.2.
> > or add a sentence like
> > 'when using single quotes, the names  are case sensitive (with is
> > lowercase for most (all?) languages).
> 
> Yeah, I'm having trouble coming up with a wording that is sufficiently
> brief.  We don't want the backward compatibility text to be longer than
> the main description, I think.
> 

something like :?

The name of the language that the function is implemented in. 
Can be 'sql', 'c', 'internal', or the name of a user-defined procedural language. 
Single quotes are optional, they required correct case when used.

regards,

Marc Mamin


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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: MVCC snapshot timing
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: seek advice about translation management