RE: Egregious coding

Please
be aware of the following note when set to FORCE...
<SPAN

class=091015422-06092001> 

<STRONG

class=Bold>Note: Forcing cursor sharing among similar (but not identical) statements can have unexpected results in some DSS applications and if your applications use stored outlines.
<SPAN

class=091015422-06092001> 

  <FONT face=Tahoma
  size=2>-----Original Message-----From: John Lewis   [mailto:jlewis_at_punchnetworks.com]Sent: Thursday, September 06, 2001   4: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 - 17:49:57 CDT