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.
>
> >I thin
> 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
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> Current EXECUTE statemtn doesn't support other way for parametrisation than
> concating strings. It works well but it's little bit unreadable. Oracle's
> statement EXECUTE has positional replacement feature.
> ...
> There are some problems about repla
Hello
Current EXECUTE statemtn doesn't support other way for parametrisation than
concating strings. It works well but it's little bit unreadable. Oracle's
statement EXECUTE has positional replacement feature. It works similar our
RAISE statement (when position holder is %). EXECUTE position h
