Hello, Kuroda-san.
At Mon, 12 Jul 2021 04:05:21 +0000, "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com> wrote in
> > Similary, the following sequence doesn't yield an error, which is
> > expected.
> >
> > > EXEC SQL AT conn1 DECLARE stmt STATEMENT;
> > > EXEC SQL AT conn2 EXECUTE stmt INTO ..;
> >
> > In this case "conn2" set by the AT option is silently overwritten with
> > "conn1" by check_declared_list(). I think we should reject AT option
> > (with a different connection) in that case.
>
> Actually this comes from Oracle's specification. Pro*C precompiler
> overwrite their connection in the situation, hence I followed that.
> But I agree this might be confused and I added the warning report.
> How do you think? Is it still strange?
(I'm perplexed from what is done while precompilation and what is done
at execution time...)
How Pro*C behaves in that case? If the second command ends with an
error, I think we are free to error out the second command before
execution. If it works... do you know what is happening at the time?
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
