Great point, but to attribute the problem properly, this is really not a SQL problem, it's a problem with the code that /calls/ the SQL. That might be Java, PHP, PL/SQL, Pro*C, ... Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com * Nullius in verba * Upcoming events: - Performance Diagnosis 101: 1/4 Calgary - SQL Optimization 101: 12/13 Atlanta - Hotsos Symposium 2005: March 6-10 Dallas - Visit www.hotsos.com for schedule details... -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Sunday, December 05, 2004 8:59 PM To: fahd-m@xxxxxxxxxxx Cc: Oracle-L Freelists Subject: Re: Definition 6. SQL that is parsed more than once. On Fri, 3 Dec 2004 16:27:53 +0500, Fahd Mirza <fahd-m@xxxxxxxxxxx> wrote: > Hi, > What would be the definition of a poorly written SQL? > -sql, with wrong join order > -sql, which uses dual > - sql, having no bind variables etc etc. > regards, > Fahd > -- > //www.freelists.org/webpage/oracle-l > -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l