Re: Set Explain

peter@prospect.anprod.csiro.au (Peter Wiley) wrote: :In article <32FD75F1.E50@gte.net> dgwilson@gte.net writes: :>jrichard@mail.ci.aurora.co.us wrote: :>> :>> We have programmers who are sending code to production with set :>> explains still in the code. Since we get binaries, we have trying to :>> figure out a way to stop the set explains from executing and creating :>> gigantic files. Any ideas??? :> :>Fire the programmers? : :Good idea. Don't pay is another :-) : :How about redirecting output to /dev/null? I agree that you should most certainly do something about your programmers. Quality control is key to any successfull development. Have you thought of all the other bad things they probably do when they make such an obvious error? However we leave the set explain on in every production program. Of course not so it is allways on, but as a hidden menu selection in the main startup menu of the program (normally using command key("&"). In this way the programmers don't need to put in set explain on all over the place, and more importantly we can easily turn it on in production should a problem arise. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org