Re: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ... - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ...
Date
Msg-id 162867790910250917j71322d8bl773963d5c647de47@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ...  (Timothy Madden <terminatorul@gmail.com>)
Responses Re: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ...
List pgsql-bugs
2009/10/25 Timothy Madden <terminatorul@gmail.com>:
>
>
> On Sun, Oct 25, 2009 at 12:42 PM, Peter Eisentraut <peter_e@gmx.net> wrot=
e:
>>
>> On l=C3=B6r, 2009-10-24 at 14:01 +0000, Timothy Madden wrote:
>> > Can the string literal syntax for CREATE FUNCTION please, please be
>> > dropped
>> > ... ?
>
> [...]
>>
>> > It is not ANSI/ISO and so annoying for compatibility.
>>
>> Whatever is inside the string literal is also not ANSI/ISO, so why would
>> it make a difference?
>>
> At least the function declaration syntax would be right. I think it would=
 be
> an important difference; this string literal idea is so strange and
> unnatural ...
>
> And why the function body would not be standard ?

Because standard knows only SQL/PSM language for SQL procedures.
Others databases support only one language for sql procedures (PL/SQL,
T-SQL). But PostgreSQL supports plpgsql, plperl, plpython as sql
procedures - and I am sure, so standard doesnt calculate with
multilangual environments.

Regards
Pavel Stehule

Do you mean it can never
> be for some reason ? How about a simple function ?
>
> Thank you,
> Timothy Madden
>

pgsql-bugs by date:

Previous
From: Timothy Madden
Date:
Subject: Re: BUG #5136: Please drop the string literal syntax for CREATE FUNCTION ...
Next
From: "Peter Bengtson"
Date:
Subject: BUG #5137: Upgrade policy clarification