misleading lang_name case in CREATE FUNCTION doc. - Mailing list pgsql-docs

From Marc Mamin
Subject misleading lang_name case in CREATE FUNCTION doc.
Date
Msg-id B6F6FD62F2624C4C9916AC0175D56D880CE2A93C@jenmbs01.ad.intershop.net
Whole thread Raw
Responses Re: misleading lang_name case in CREATE FUNCTION doc.  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-docs
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).
 
regards,
 
Marc Mamin
 
 
 
lang_name
 
    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.
    For backward compatibility, the name can be enclosed by single quotes.
 
 
 
No longer forcibly lowercase procedural language names in CREATE FUNCTION (Robert Haas)
 
While unquoted language identifiers are still lowercased,
strings and quoted identifiers are no longer forcibly down-cased.
Thus for example CREATE FUNCTION ... LANGUAGE 'C' will no longer work;
it must be spelled 'c', or better omit the quotes.
 
 
 

pgsql-docs by date:

Previous
From: rudolf
Date:
Subject: Re: "format" function documentation fix
Next
From: "liuyuanyuan@highgo.com.cn"
Date:
Subject: seek advice about translation management