Re: misleading lang_name case in CREATE FUNCTION doc.

From: Marc Mamin <M(dot)Mamin(at)intershop(dot)de>
To: "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Cc: "'pgsql-docs(at)postgresql(dot)org'" <pgsql-docs(at)postgresql(dot)org>
Subject: Re: misleading lang_name case in CREATE FUNCTION doc.
Date: 2013-11-13 14:02:43
Message-ID: B6F6FD62F2624C4C9916AC0175D56D880CE4740C@jenmbs01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

> From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2013-11-13 15:14:19 Re: MVCC snapshot timing
Previous Message Peter Eisentraut 2013-11-13 11:56:04 Re: misleading lang_name case in CREATE FUNCTION doc.