Instructions are given in Italics!

Your project should at least have the following template and functionality. If you want to do fancier stuff, do so only after providing for the following features:

<Project Name>

Team Members: <Team-member names>


In the following, substitute actual names for Relation1, Relation2 etc. Have as many entries as the number of relations in your project. Clicking a link on a relation name should execute an SQL query and list *all* the tuples in that particular relation (of course, the links below don't work). Your output should be presented on a separate web page in a neat, orderly fashion, one row for each tuple and columns plainly evident. Ensure that all columns have their names listed and their data types are clear (i.e., state which is an int and which is a char and so on).

  1. Relation1
  2. Relation2
  3. Relation3
  4. Relation4
  5. ... rest of your relations

The relation names listed here, and the column names listed when a user clicks on the links, should work when used in the SELECT or FROM clauses of a query entered in the text box below.


In the following, add an English query description for each of the five queries that you created for Part 6 of your project. Again, clicking a link on the query name should execute the appropriate SQL query and list the tuples that are the answer to that particular query. Again, make sure your output is neatly ordered and column names and data types are evident. The output of the query should appear on a separate page. Near the top of the page, above the tidily presented query output, must be the original SQL for your query.

  1. Query1: <put an English description of that query here>.
  2. Query2: <put an English description of that query here>.
  3. Query3: <put an English description of that query here>.
  4. Query4: <put an English description of that query here>.
  5. Query5: <put an English description of that query here>.

Ad-hoc Query:

Provide a free-form box and two buttons called "Submit" and "Clear" here. The intent is that the user can enter most arbitrary SQL queries in the box and click the submit button. The action should be that you should execute that query on the database and bring up the answers on a separate page, once again, in a neat, orderly fashion. Notice that the input can be most legal SQL queries (permissible under your DB system, of course). (SELECT, INSERT, and UPDATE should definitely be allowed.)

The grader will use table names from your own documentation (Project Part 3, etc), so do not change the names of your tables or your columns unless you update all of your documentation to match the new names. (Did you test your ad-hoc query form with a "like" query? Did you test on queries with <, = or > in the where clause?)

Please enter your query here