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, they don't work
below). Your output should be presented on a separate web page in a neat
orderly fashion, one row for each tuple and where columns are evident.
Ensure that all columns have their headers listed and their types are
clear (i.e., state which is an int and which is a char and so
on).
In the following, substitute the english
query description for each of the five queries that you did in Step 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 types are evident. The output should appear
on a separate page.
Query1: Find date/venue 's that band 2 is playing at in the future;
Here, provide a free-form box and two buttons called
"Submit" and "Clear". The intent is that the user can enter any arbitrary
SQL query 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 any legal SQL query (permissible under your DB system, of course).