Mmmm I'm afraid I wasn't clear :-(
Patch 22244617 includes a new definition of i_type6 on "type$(toid,
version#, typ_name, package_obj#)", typ_name is introduced and it's now the
third column
But I think that might not be enough for you here, right?
I'm more inclined to agree with Stefan about an unnecessary flexibility in
the application code that seems to pay the consequences of internal changes
in the DB you wouldn't normally worry about
On Tue, Oct 11, 2016 at 10:18 AM, l.flatz@xxxxxxxxxx <l.flatz@xxxxxxxxxx>
wrote:
Hi Stefan
Mauro Pagano (thanks Mauro) also thinks Patch 22244617 could help. If it
really contains this index create it would.
Regards
Lothar
----Ursprüngliche Nachricht----
Von : contact@xxxxxxxx
Datum : 11/10/2016 - 15:30 (UTC)
An : l.flatz@xxxxxxxxxx
Cc : oracle-l@xxxxxxxxxxxxx
Betreff : Re: Re: Recursive statements slowing down batch processing
Hey Lothar,
this looks like some fancy code generation tool, right? I am pretty sure
that they have some "unnecessary" flexibility at OCI layer to handle all
that
fancy generations.
-> Rogue Wave® Stingray® Studio integrated GUI components are designed to
handle the low-level details of GUI application development, shortening
development time and making it easier to maintain and evolve GUI
applications over time
By the way if your procedure parameters param1 to param 3 for
"package_name.procedure()" are all just numbers or varchars - then this is
a perfect
example for unnecessary describes.
... so i am out ...
See you in a few weeks.
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
"l.flatz@xxxxxxxxxx" <l.flatz@xxxxxxxxxx> hat am 11. Oktober 2016 um15:14 geschrieben:
cursor is not necessarily a parameter. Most of the time parameters are
Hi Stefan,
thanks for responding. We will definitly do 10051.
Actually the packages specs do contain ref cusor types, but such ref
number
and varchar only.Studio_HTML_User_Guide/index.html#page/Stingray%20Studio/
I wonder if we got it to do with a "functor"
(http://docs.roguewave.com/stingray/current/Stingray_
otug-otatl.087.06.html).
I agree, this flexibility (describe etc) is not needed. Not that Ireally git whatr a functor should be and when it should be used.
--
Keep you posted and see you at DOAG.
Regards
Lothar
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l