Re: Stalled post to pgsql-bugs - Mailing list pgsql-general

    Thanks! I thought that my bug was ignored...

    It would be nice to have RETURNING used in PL/SQL functions...
Without named parameters I can live -- they are just syntactic sugar
-- but RETURNING can not be worked around...

    Ciprian.


On 10/19/07, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Hello
>
> it's feature :(. And it isn't supported in 8.3 too
>
> all info about unsupported features you can find in ToDo list
> http://www.postgresql.org/docs/faqs.TODO.html
>
> # Allow SQL-language functions to return results from RETURNING queries
>
> http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
> # Allow SQL-language functions to reference parameters by parameter name
>
> Currently SQL-language functions can only refer to dollar parameters, e.g. $1
>
> Regards
> Pavel Stehule
>
> 2007/10/19, Ciprian Dorin Craciun <ciprian.craciun@gmail.com>:
> >     Hello all!
> >
> >     Almost two months ago I have posted a bug on the bug reporting
> > form that is available on the web page... (I forward here the email I
> > got in response.) It was related about the RETURNING feature available
> > for INSERT, UPDATE and DELETE, and the fact that I can not use it as
> > last statement is PL/SQL functions.
> >
> >     But until now I saw no activity on this bug... How can I track it?
> > Has some one looked at it? Is it already fixed?
> >
> >     I've monitored the release notes of every release from 8.2.5 and
> > saw nothing related to the issue.
> >
> >     Could some one point me into the right direction? Or I could try
> > to fix it my self if someone could tell me where to start...
> >
> >     Thank you all,
> >     Ciprian.
> >
> >     P.S.: I have also tried to send this same message directly to
> > psql-bugs mailing list but obtained the same message that the report
> > is stalled.
> >
> >
> > ---------- Forwarded message ----------
> > From: pgsql-bugs-owner@postgresql.org <pgsql-bugs-owner@postgresql.org>
> > Date: Sep 3, 2007 8:13 PM
> > Subject: Stalled post to pgsql-bugs
> > To: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
> >
> >
> > Your message to pgsql-bugs has been delayed, and requires the approval
> > of the moderators, for the following reason(s):
> >
> > The author ("Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>)
> >   is not a member of any of the restrict_post groups.
> >
> > If you do not wish the message to be posted, or have other concerns,
> > please send a message to the list owners at the following address:
> >   pgsql-bugs-owner@postgresql.org
> >
> >
> > ---------- Forwarded message ----------
> > From: "Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>
> > To: pgsql-bugs@postgresql.org
> > Date: Mon, 3 Sep 2007 17:13:40 GMT
> > Subject: BUG #3596: "insert ... returning *" not usable as last
> > statement in a function...
> >
> > The following bug has been logged online:
> >
> > Bug reference:      3596
> > Logged by:          Ciprian Dorin Craciun
> > Email address:      ciprian.craciun@gmail.com
> > PostgreSQL version: 8.2.4
> > Operating system:   Debian Etch (4.0)
> > Description:        "insert ... returning *" not usable as last statement in
> > a function...
> > Details:
> >
> > I think the best explanation is the example just above...
> >
> > The idea is that in 8.2 insert statement was modified by adding an returning
> > option, that modifies insert to behave also as a select statement by
> > returning all the rows inserted. But unfortunately this option can not be
> > used inside functions that return something as a last statement...
> >
> > create table table1 ( field int );
> >
> > create function function1 ( int ) returns table1 as $$
> >         insert into table1 values ($1) returning *;
> > $$ language sql;
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> >                http://archives.postgresql.org/