Re: multiple CREATE FUNCTION AS items for PLs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: multiple CREATE FUNCTION AS items for PLs
Date
Msg-id 17743.1355683024@sss.pgh.pa.us
Whole thread Raw
In response to Re: multiple CREATE FUNCTION AS items for PLs  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: multiple CREATE FUNCTION AS items for PLs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: multiple CREATE FUNCTION AS items for PLs  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
Hannu Krosing <hannu@2ndQuadrant.com> writes:
> On further thought the function name should just be what it is defined 
> in postgresql, like this

> CREATE FUNCTION foo(a,b,c) AS $$
>      import x
>          from __future__ import nex_cool_feature

>          def helper_function(x):
>             ...

>          def foo(a,b,c):
>              defined function body here

>          def bar(i,j):
>              function body for bar(i,j)
> $$ language plpythonu;

>> but this would not be backwards compatible, at least not in any 
>> obvious way.

> This is still unfortunately true :(

Could we say that *if* the function text contains a line beginning
"def function_name" then we interpret it as above, otherwise oldstyle?
I'm not sure how big a risk of false positives there'd be.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: multiple CREATE FUNCTION AS items for PLs
Next
From: Tom Lane
Date:
Subject: Re: multiple CREATE FUNCTION AS items for PLs