WHERE to Go from Here
This chapter has introduced the role of the WHERE clause in different types of SQL statements as well as the various components used to build a WHERE clause. Because the WHERE clause plays such an important role in many SQL statements, however, the topic is far from exhausted. Additional coverage of WHERE clause topics may be found in:
Chapter 3, in which various flavors of join conditions are studied in detail
Chapter 5, which probes the different types of subqueries along with the appropriate operators for evaluating their results
Chapter 6, in which various methods of handling date/time data are explored
Chapter 14, which explores certain aspects of the WHERE clause from the standpoint of performance and efficiency
Additionally, here are a few tips to help you make the most of your WHERE clauses:
Check your join conditions carefully. Make sure that each data set in the FROM clause is properly joined. Keep in mind that some joins require multiple conditions. See Chapter 3 for more information.
Avoid unnecessary joins. Just because two data sets in your FROM clause contain the same column does not necessitate a join condition be added to your WHERE clause. In some designs, redundant data has been propagated to multiple tables through a process called denormalization. Take the time to understand the database design, and ask your DBA or database designer for a current data model.
Use parentheses. Oracle maintains both operator precedence and condition ...