Most "decent" query engines will know how to optimally run the query either way, whether you put it in the from or where clause. That said, there is no excuse for writing sloppy code, or using the wrong type of joins. (even the smartest query engine can't get around bad query designs... sometimes due to indexes or other quirks of the data, you can help the query more than you think)
My personal preference is to put joins in the from clause, if only for readability, and let the where clause handle general criteria. It's not for the computer, but for the programmer or DBA who follows me (which is often me, so I help myself!). -----Original Message----- From: Mark Fuqua [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19, 2005 19:03 To: CF-Talk Subject: OT Joins Can anyone explain to me what type of join is created when the join is done with the WHERE clause as opposed to the FROM clause in a sql statement. What are the advantages the joins in the FROM clause. I know it is because I am still very green but I find WHERE clause joins much easier to write. Thanks, Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:221645 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
