I believe Raj is referring to the fact that Oracle will reuse SQL from the SQL Cache if the statement has been parsed already, but they must match verbatim.
for example: a) SELECT column1, column2 FROM table WHERE column0 = 5; b) SELECT COLUMN1, COLUMN2 FROM TABLE WHERE COLUMN0 =5; will be stored in the sql cache with 2 different hash id's, so each will be stored separately in the cache. I have always found it recommended that a certain upper/lower case naming convention be followed to avoid this situation. -Joe --- "Mercadante, Thomas F" <[EMAIL PROTECTED]> wrote: > Raj, > > Do you have any test cases or white papers to support your > statement? > Especially the part about > > "if you mix-n-match that will make Oracle do more work." > > never heard of this before and I am interested if it is true. > > Tom Mercadante > Oracle Certified Professional __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Joe Raube INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
