Hints on Queries

1. 5 queries is a MINIMUM. While five great queries would be enough, you will be a lot safer if you do a few more.

2. Diversity of queries is also important – you can’t get full credit for five variations on the same query.

3. Try to relate the queries you write here to the functional requirements you listed earlier. Queries with clear practical use related to your spec will receive more credit.

4. At least one query must include an update or delete.(OK, so technically these are just SQL statements, not queries. You know what I mean).

5. Try to cover as many of the following as possible. All these were covered in class – the project is your chance to experiment with and apply them. Extra credit is available here.

At least one query with some calculated fields

Nice formatting of data and time

Creation of a view, use of same view in other queries.

Use of view for logical data abstraction.

A summary query using group by and at least one aggregate function.

Queries that demonstrate use of constraints, cascading deletes, etc.

Subqueries, especially when the use of a join would be clumsy.

Complex joins, including outer joins when appropriate.

For examples of how to do all these things, see the example sql file.