Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Egregious coding

RE: Egregious coding

From: John Lewis <jlewis_at_punchnetworks.com>
Date: Thu, 06 Sep 2001 15:18:14 -0700
Message-ID: <F001.00385F41.20010906153023@fatcity.com>

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:18:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US