You're right, Oracle reads from the bottom up. It's good practice to place your most limiting conditions at the end of the where clause, and work your way up from there.
v/r, Jeff -----Original Message----- From: Chris Lofback [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 10:34 AM To: CF-Talk Subject: SOT: Oracle query question Lowdown: What is the optimum arrangement of WHERE clauses when querying an Oracle database? Details: I'm trying to optimize my CF queries running against an Oracle 8i database. I know that conventional wisdom is to put highly selective columns (those with many unique values) first in the WHERE clause so that the result set is as small as possible for the following clauses. But I recall reading somewhere that Oracle actually processes WHERE clauses in reverse order--from last to first. Does anyone on the list know for sure about this? And does the order/placement of indexed columns significantly affect the query speed? Thanks, Chris Lofback Sr. Web Developer TRX Integration 28051 US 19 N., Ste. C Clearwater, FL 33761 www.trxi.com ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
