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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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
>strings.
>
Maybe, but patch have to solve SQL string and non SQL strings too
Regards
Pavel Stehule
_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-03-28 13:58:51 | Tru64/Alpha problems |
Previous Message | Tatsuo Ishii | 2006-03-28 11:58:14 | Re: Why are default encoding conversions |
From | Date | Subject | |
---|---|---|---|
Next Message | BERTHOULE Emmanuel | 2006-03-28 20:31:53 | restore to defaults values when commenting of variables in postgresql.conf |
Previous Message | Tom Lane | 2006-03-27 21:09:36 | Re: proposal - plpgsql: execute using into |