RE: Egregious coding

<FONT

face=Verdana>Good
idea.  Cursor_Sharing <SPAN
class=781445422-06092001>= force results in the SQL statements being converted, substituting the hard-coded values with temporary bind variables
before  they are
parsed<SPAN
class=781445422-06092001>.
<FONT

face=Verdana>It <SPAN
class=781445422-06092001>help<SPAN
class=781445422-06092001>s where
the SQL problem is a scarcity
of bind variables, <SPAN
class=781445422-06092001>but that is probably not the only coding problem that contributes to your miseries(bet they never heard of joins, outer, inner or
multidimensional??). 
<FONT face=Tahoma

size=2>-----Original Message-----From: John Lewis [mailto:jlewis_at_punchnetworks.com]Sent: Thursday, September 06, 2001 6:30 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Egregious coding
You
can put "cursor_sharing=force" in the init file. It forces the reuse of sql even without
bind
variables. I had the same problem with the "javoids".

  <FONT face=Tahoma
  size=2>-----Original Message-----From: Hagedorn, Linda   [mailto:lindah_at_epocrates.com]Sent: Thursday, September 06, 2001   4:06 PMTo: Multiple recipients of list ORACLE-LSubject:   Egregious coding
  Has anyone thought of a clever way to fail every   SQL statement that does not use a bind variable that I could switch on and off   as required?      
  I'm looking at hundreds of thousands of queries in   the v$sqlarea in production.  I've taken engineering management to task   over this, and have gotten empty promises in return.  I would love to   hold a valid threat over their heads that I'm going to shut off every   statement that is not coded properly.    Any ideas are appreciated.
  Linda
      
    Received on Thu Sep 06 2001 - 18:04:34 CDT