Hello,

This task can be better solved. There are some problems with strings, but bigger problem is impossibility to pass nonscalar variables. What is questions? Does Oracle allow variables on nonparam positions? If not, then I see more elegant solution via preprocessed statements.

Best regards
Pavel Stehule


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   [EMAIL PROTECTED]
  EnterpriseDB    http://www.enterprisedb.com

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


<< execute_using.dif >>



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

_________________________________________________________________
Chcete sdilet sve obrazky a hudbu s prateli? http://messenger.msn.cz/


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

              http://www.postgresql.org/docs/faq

Reply via email to