Skip site navigation (1) Skip section navigation (2)

Re: proposal - plpgsql: execute using into

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal - plpgsql: execute using into
Date: 2006-03-28 13:01:55
Message-ID: BAY20-F155D9BBD738840E24AECCDF9D30@phx.gbl (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
> > 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

Maybe, but patch have to solve SQL string and non SQL strings too

Pavel Stehule

Citite se osamele? Poznejte nekoho vyjmecneho diky

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-03-28 13:58:51
Subject: Tru64/Alpha problems
Previous:From: Tatsuo IshiiDate: 2006-03-28 11:58:14
Subject: Re: Why are default encoding conversions

pgsql-patches by date

Next:From: BERTHOULE EmmanuelDate: 2006-03-28 20:31:53
Subject: restore to defaults values when commenting of variables in postgresql.conf
Previous:From: Tom LaneDate: 2006-03-27 21:09:36
Subject: Re: proposal - plpgsql: execute using into

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group