Slide 2-24: TITLE attribute of the first four tuples should be as follows:

Slide 2-45: Second query - variable t should range over Emp, not customer.

Slide 2-47: t[Pname]=s[Pname] should be t[Pno]=s[Pno]

Slide 3-30: The relationship name should be MANAGES.

Slide 4-3o: The output part of the tuple calculus expression should be a tuple: { | ...}

Slides 4-33 and 4-34: Delete these slides; CONTAINS construct is no longer supported.

Slide 4-59: The declaration of pno1 and pno2 should be simple int (no array specification).

Slide 4-65: The general form of access should read EXEC SQL FETCH [FROM] ... (i.e., FROM is an optional keyword that can be used).

Slide 4-74: There should be semicolons at the ends of lines 8, 13, 15. Also, read into :resp (line) 10) should be a comment inside /* and */.

Slide 4-77: Remove the semicolon at the end of line City CHAR(9));

Slide 4-79: Change the comma to a semicolon at the end of line ON UPDATE CASCADE.

Slide 5-13: The formal definition of transitive dependency should be: X->Y and Y->Z and X->Z and Y NOT -> X and Z NOT SUBSET Y.

Slide 5-20: In second bullet, add "non-trivial" in between "every" and "functional" to read "every non-trivial functional ...".

Slide 5-22: In the figure, (a) ENO should be a key, and (b) there should be no arrow head going into ENO. So, PNJO and ENO should jointly functionally determine LOCATION and RESP.

Slide 5-28: In the second bullet, the procedure name should be ComputeX⁺ (not AttrClosure)

.

Slide 7-3: SUM in th enexted query should be COUNT.

Slide 7-4:The Plan should be as follows:

1. T₁ <- Scan Project table and select all tuples with Budget value > 250000.
2. T₂ <- Join T₁ with the Works relation
3. T₃ <- Join T₂ with the Emp relation
4. T₄ <- Group tuples of Works over Pno and for groups that have more than 2 tuples, Project over Pno
5. T₅ <- Join T₃ with T₄
6. Project T₅ over Ename, Title

Slide 7-5: The plan changes accordingly. This is too complicated to draw, so click here to see the correct version of the slide.