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

Re: [HACKERS] proposal - plpgsql: execute using into

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)hotmail(dot)com>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] proposal - plpgsql: execute using into
Date: 2006-08-21 17:45:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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.

Oracle does use USING:

	EXECUTE IMMEDIATE dynamic_string
	[INTO {define_variable[, define_variable]... | record}]
	[USING [IN | OUT | IN OUT] bind_argument
	[, [IN | OUT | IN OUT] bind_argument]...]
	[{RETURNING | RETURN} INTO bind_argument[, bind_argument]...];

so I think we are OK there.

> >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

The only case I see you using it is for \:.  What is the purpose of
that?  Can't we use :: for a literal :?

I have attached the patch from March.

  Bruce Momjian   bruce(at)momjian(dot)us

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

Attachment: execute_using.dif
Description: text/x-diff (22.0 KB)

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-08-21 17:52:26
Subject: Re: ISBN/ISSN/ISMN/EAN13 module
Previous:From: Markus SchiltknechtDate: 2006-08-21 17:42:47
Subject: Re: Replication

pgsql-patches by date

Next:From: Marko KreenDate: 2006-08-21 18:10:10
Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to
Previous:From: Tom LaneDate: 2006-08-21 17:29:48
Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to

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