RE: Egregious coding

<FONT face=Arial color=#0000ff

size=2>Significant documentation has already been produced showing the overhead associated with the code.  The effect of shutting off 'literal only' sql on the QA system would centralize the problem in a single location, and allow the parties involved to correct the code before moving to staging or production.  Setting cursor_share=force is a workaround.  Thanks.   
<FONT face=Arial color=#0000ff

size=2> 
What
about something that would interfere with the parser?  What about language code pages?  Replace the  ' and ''  with something else that would cause the parse to fail?  Has anyone coded an exit on the parser? 
        
<FONT face=Arial color=#0000ff

size=2> 
All
ideas are welcome. 
 
<FONT face=Arial color=#0000ff

size=2>Linda
<FONT face=Arial color=#0000ff

size=2>Finished reviewing only 10% of 95M of non-reusable SQL, and in the process of creating
bug tickets.       
<FONT face=Arial color=#0000ff

size=2><FONT face=Arial
color=#0000ff size=2> 
-----Original
Message-----From: Greg Moore
[mailto:sqlgreg_at_pacbell.net]Sent: Thursday, September 06, 2001 6:00 PMTo: Multiple recipients of list ORACLE-LSubject: Re: Egregious coding

  >  I would love to hold a
  >  valid threat over their
  heads
   
  The key word is valid.  Threatening to throw   a switch and blow up any SQL that contains literals is a threat, but is   it a valid threat?
   
  I mean, what was your previous job, suicide   bomber?
   
  Seriously, providing accurate measurement of how   much the extra parsing now costs, along with an evaluation of current CPU use   and an estimate of how much longer they have before the system bottlenecks   might be a touch more civilized.
   
   
  <BLOCKQUOTE
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">     <FONT face=Arial color=#0000ff
size=2>  Received on Fri Sep 07 2001 - 17:42:19 CDT