pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <janwieck@Yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Ansley <Michael.Ansley@intec-telecom-systems.com>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: sqllist <pgsql-sql@postgreSQL.org>
Cc: pgsql-hackers@postgresql.orgg
Subject: Re: [HACKERS] Re: PL/PGSQL function with parameters
Date: Thu, 8 Feb 2001 07:22:13 -0500 (EST)
Message-ID: <200102081222.HAA03553@jupiter.greatbridge.com> (raw)
In-Reply-To: <25204.981476161@sss.pgh.pa.us>

Tom Lane wrote:
> Michael Ansley <Michael.Ansley@intec-telecom-systems.com> writes:
> > CREATE FUNCTION table_count(varchar) RETURNS integer AS '
> > DECLARE
> >  SQL varchar;
> >  RES integer;
> > BEGIN
> >  SQL = ''SELECT * INTO temp1 FROM '' || $1;
> >  EXECUTE SQL;
> >  SELECT count(*) INTO RES FROM temp1;
> >  RETURN(RES)
> > END;
> > '
> > LANGUAGE 'plpgsql';
>
> > What I couldn't get it to do was to select directly into the variable RES.
>
> I tried this, and it seems that "SELECT ... INTO foo" is not executed
> correctly by EXECUTE --- the INTO is handled as an ordinary select-into-
> table construct rather than plpgsql's select-into-variable.
>
> While I have not looked closely, I seem to recall that plpgsql handles
> INTO by stripping that clause out of the statement before it's passed to
> the SQL engine.  Evidently that's not happening in the EXECUTE case.
>
> Jan, do you agree this is a bug?  Is it reasonable to try to repair it
> for 7.1?  If we do not change the behavior of EXECUTE now, I fear it
> will be too late --- some people will come to depend on the existing
> behavior.

    EXECUTE simply takes the string expression and throws it into
    SPI_exec() without parsing. Changing that for  7.1  is  *not*
    possible.

    The above can be accomplished by

        DECLARE
          ROW record;
          RES integer;
        BEGIN
          FOR ROW IN EXECUTE
              ''SELECT count(*) AS N FROM '' || $1
          LOOP
            RES := N;
          END LOOP;
          RETURN RES;
        END;

    Not  as  elegant  as  it  should  be,  but at least possible.
    There's much to be done for a future version of PL/pgSQL, but
    better  support  for  dynamic SQL needs alot of functionality
    added to the main parser and the SPI  manager  in  the  first
    place.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (15+ messages)  latest in thread

Message-ID: <200102081222.HAA03553@jupiter.greatbridge.com>
Permalink:  ../200102081222.HAA03553@jupiter.greatbridge.com/
Also on:    postgresql.org/message-id/200102081222.HAA03553@jupiter.greatbridge.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: janwieck@Yahoo.com, tgl@sss.pgh.pa.us, Michael.Ansley@intec-telecom-systems.com, pgsql-hackers@postgresql.orgg
  Subject: Re: [HACKERS] Re: PL/PGSQL function with parameters
  In-Reply-To: <200102081222.HAA03553@jupiter.greatbridge.com>
  References: <25204.981476161@sss.pgh.pa.us> <200102081222.HAA03553@jupiter.greatbridge.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox