Disclaimer: I have attempted to be comprehensive in the following, but important items may have been omitted by mistake. If you see such an omission, please let me know, but you are responsible for all of the lecture material to date.

The third hour exam will be on Tuesday, April 24, and will cover

Date:  Chapters 5 - 7, Sunderraman, chapters 3 - 4, algebra handout, calculus handout, Supplementary book, ProgrammingInterfaces.PPT, ALGEBRA.PPT, THEORY.PPT, DESIGN02.PPT

• Design.
  • Be able to take a form and do a bottom-up design based on it.
• SQL
  • Be able to explain the basics of PL/SQL. In particular, be able to describe what a cursor is and how it may be used.
• Forms
  • Be able to describe the steps involved in creating a master-detail form in Oracle. Be able to describe what is necessary to create a master-detail form.
  • Be able to describe the process of creating a menu (you will have the option of describing the menu system or of describing how to use bottons).
• Theory
  • Be able to describe why a relational database is called relational.
  • Be able to write queries the full relational algebra (either as described in the textbook or in the relational algebra interpreter).
  • Be able to distinguish between relational algebra and relational calculus expressions in SQL.
  • Be able in SQL expressions to identify conditions which would translate to join operations or to selection statements.
  • Be able to translate a SQL, Algebra, or Calculus statement into English (being careful to note the difference between translation and transliteration).
  • Be able to distinguish between the tuple calculus and the domain calculus (though I will not ask you to write any queries in Prolog).
  • Be able to write queries in the relational calculus (either using the syntax described in the textbook or in the relational calculus interpreter).
  • You may be asked to do another forall or minus query in SQL by way of comparison.

  Queries will be either with respect to the SPJ database, or to the Hoh River College database.