Re: proposal - plpgsql: execute using into

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)hotmail(dot)com>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal - plpgsql: execute using into
Date: 2006-04-21 23:53:43
Message-ID: 200604212353.k3LNrh804302@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Pavel Stehule wrote:
> > > There are some problems about replacing string values in the SQL string.
> >
> >Doesn't the Oracle implementation already imply a solution to that?
> >
>
> I don't know. I didn't find any detail documentation about it. I don't know
> what Oracle exactly do.
>
> >I think we'd be best off to leave EXECUTE alone, at least until we've
> >converged to the point where almost nobody is using non-standard-compliant
> >strings.
> >
>
> Maybe, but patch have to solve SQL string and non SQL strings too

Pavel, I am still confused what the USING clause is for, and you need to
research how Oracle handles it before we can add this. Would you
provide an example of its usage?

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-04-22 01:39:53 Re: Further reduction of bufmgr lock contention
Previous Message Bruce Momjian 2006-04-21 23:30:10 Re: Win32 sysconfig -> pg_service.conf

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-04-21 23:56:20 Re: WAL logging of SELECT ... INTO command
Previous Message Bruce Momjian 2006-04-21 23:33:22 Re: restore to defaults values when commenting of variables