Term of the Moment
AND-OR-NOT
Definition: query
To search for data. In addition to obtaining lists of records that match the search criteria, queries to a database allow for counting items and summing amounts. A query to a search engine such as Google or Bing yields a summary of the contents of Web pages and is more often called a "search."
Simple or Complex
Defining a query for a relational database can be extremely simple or very complex. If the query is based on one matching condition, such as "retrieve all customers who owe us more than $10,000," it is usually easy to define in a query language or program. However, "retrieve all customers who owe us more than $10,000 from purchasing toasters" is not easy. It requires several steps to determine how many toaster orders are in the balance due.
Tables Must Be Joined
Relational databases are designed to eliminate redundancy. The goal is to store a data item in one table and not have it duplicated in others. For example, an order record will contain the product number ordered, but often not its description. The description is stored in a product table. Thus, any printout of products ordered and their descriptions requires that the order table be linked to the product table for that query or report. Linking customer, order and product tables is a common example of "joining" tables to satisfy a query.
Contents of a Query
Most queries require at least the following conditions to be stated. First, which table or tables is the data coming from. If from two or more tables, what is the link between (typically account number or name). Next, define the selection criteria, which is the matching condition or filter. Lastly, define which fields in the tables are to be displayed or printed in the result. See SQL.
The Query Statement
Simple or Complex
Defining a query for a relational database can be extremely simple or very complex. If the query is based on one matching condition, such as "retrieve all customers who owe us more than $10,000," it is usually easy to define in a query language or program. However, "retrieve all customers who owe us more than $10,000 from purchasing toasters" is not easy. It requires several steps to determine how many toaster orders are in the balance due.
Tables Must Be Joined
Relational databases are designed to eliminate redundancy. The goal is to store a data item in one table and not have it duplicated in others. For example, an order record will contain the product number ordered, but often not its description. The description is stored in a product table. Thus, any printout of products ordered and their descriptions requires that the order table be linked to the product table for that query or report. Linking customer, order and product tables is a common example of "joining" tables to satisfy a query.
Contents of a Query
Most queries require at least the following conditions to be stated. First, which table or tables is the data coming from. If from two or more tables, what is the link between (typically account number or name). Next, define the selection criteria, which is the matching condition or filter. Lastly, define which fields in the tables are to be displayed or printed in the result. See SQL.
This diagram depicts the typical conditions that have to be stated when querying a relational database.