> > 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
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2006-03-28 13:58:51|
|Subject: Tru64/Alpha problems|
|Previous:||From: Tatsuo Ishii||Date: 2006-03-28 11:58:14|
|Subject: Re: Why are default encoding conversions|
pgsql-patches by date
|Next:||From: BERTHOULE Emmanuel||Date: 2006-03-28 20:31:53|
|Subject: restore to defaults values when commenting of variables in postgresql.conf|
|Previous:||From: Tom Lane||Date: 2006-03-27 21:09:36|
|Subject: Re: proposal - plpgsql: execute using into |