Re: Embedded SQL Question

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/16/2017
11:24:06 AM:

It's never really been a concern to me. And it is quite common for
everyone to use the same cursor name
Declare C1 cursor for...
kind of stuff.

Never heard of someone getting bit by that.

We have -- not with reading each other's cursors, but with ODP's
(or something) not getting rebuilt when they should. Unique cursor names
will insure that SQL correctly handles everything it should. You see, in
our case we have the same object name in multiple libraries -- with
initial library lists controlling which libraries are available at any
given time. But we have run into issues when we need to go across
libraries against the same object name. Activation groups are one thing,
but unique cursor names are the rest of the picture.

Sincerely,

Dave Clark