Study aids

DB Design Studio ER diagrams in the class notation, checked as you draw

Your tables

How to write it

A stage on its own line: 1NF, 2NF, 3NF, BCNF or 3NF/BCNF.

A table: BOOKING (Member_ID*, Class_ID*, Session_Date*, Paid). The * marks the primary key.

Under the 1NF table, its dependencies, one per line, with your label after a colon: Member_ID -> Member_Name, Phone : partial. Labels: partial, transitive, CK (or other). The key's own arrows are implied.

Later stages only need their tables: their dependencies are worked out from the 1NF ones. Type some to have your labels checked.

Optional sample rows after a line data: a header row, then rows, separated by |. Each dependency is tested against them.

Click a diagram or a check to jump to its line.

Expression

How to write it

As in class: π Name (σ Tier = 'GOLD' (MEMBER)). A join condition goes right after ⋈: R ⋈ R.a = S.b S. Rename with ρ E (EMPLOYEE), then write E.Name.

π, σ and ρ apply to the bracket right after them; ⋈ × ∪ ∩ − ÷ read left to right, so add brackets to group.

No special keyboard needed: the buttons above, or words: PROJECT SELECT RENAME JOIN TIMES UNION INTERSECT MINUS DIVIDE, <> for ≠, AND OR NOT.

Name a step with T ← expression on its own line; the last line is the answer.

Click a node of the tree to see its table.