Section 1 - CS4320 Sections Fall 2011 Sections o Monday 7:30-8:20pm Upson 315(Section lead Wenlei Xie o Tuesday 11:15-12:05pm Upson 315(Section

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Database Management Systems, R. Ramakrishnan and J. Gehrke 1 CS4320 Sections Fall 2011 ! Sections : o Monday, 7:30-8:20pm, Upson 315 (Section lead: Wenlei Xie) o Tuesday, 11:15-12:05pm; Upson 315 (Section lead: Tuan Cao) o Friday, 1:25-2:15pm; Upson 315 (Section lead: Ben Sowell) ! Instructor : Johannes Gehrke o Office hours: Fridays, 1:15-2:15pm, 4105B Upson Hall or by appointment. ! TAs : Tuan Cao, Qiming Fang, Keonseo Park, Ben Sowell, Wenlei Xie o Office hours: Mondays and Wednesdays, 5-6pm in 328B Upson Hall. o Please do not send emails to the TAs directly; you can contact the TAs by sending email to “cs4320-fall2011-tas-l at cornell.edu”.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database Management Systems, R. Ramakrishnan and J. Gehrke 2 Outline ! Review ER diagram modeling ! Do some ER diagram exercises e.g. Exercise 2.3 in the text book ! Finish up the Relational Algebra lecture ! Do some Relational Algebra and Calculus exercises e.g. Exercise 3.13 and Exercise 4.3 in the text book
Background image of page 2
Database Management Systems, R. Ramakrishnan and J. Gehrke 3 Conceptual Design Using the ER Model ! Design choices: Should a concept be modeled as an entity or an attribute? Should a concept be modeled as an entity or a relationship? Identifying relationships: Binary or ternary? Aggregation? ! Constraints in the ER Model: A lot of data semantics can (and should) be captured. But some constraints cannot be captured in ER diagrams.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database Management Systems, R. Ramakrishnan and J. Gehrke 4 Entity vs. Attribute " Consider address information to the Employees entity set. " Should address be an attribute of Employees or an entity (connected to Employees by a relationship)? name Employees ssn lot
Background image of page 4
Database Management Systems, R. Ramakrishnan and J. Gehrke 5 Entity vs. Attribute ! Depends upon the use and the semantics of the data: " Address as an attribute: - If we record only one address per employee. " Address as an entity: - If we have several addresses per employee, - If the structure (city, street, etc.) is important, e.g., we want to retrieve employees in a given city.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database Management Systems, R. Ramakrishnan and J. Gehrke 6 Entity vs. Attribute (Contd.) name Employees ssn lot Works_In4 from to dname budget did Departments Attributes “ from ” and “ to ” are used to record the interval during which an employee works for a department.
Background image of page 6
Database Management Systems, R. Ramakrishnan and J. Gehrke
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 12/07/2011 for the course CS 4410 taught by Professor Vollset during the Spring '07 term at Cornell University (Engineering School).

Page1 / 19

Section 1 - CS4320 Sections Fall 2011 Sections o Monday 7:30-8:20pm Upson 315(Section lead Wenlei Xie o Tuesday 11:15-12:05pm Upson 315(Section

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online