DBS0902-Database_Systems_Review.ppt

2009-4-28 * Attribute-Based Checks Constraints on the value of a particular attribute. Add CHECK(condition) to the declaration for the attribute. The condition may use the name of the attribute, but any other relation or attribute name must be in a subquery. 2009-4-28 * Tuple-Based Checks CHECK (condition) may be added as a relation-schema element. The condition may refer to any attribute of the relation. But other attributes or relations require a subquery. Checked on insert or update only. 2009-4-28 * Assertions (断言) These are database-schema elements, like relations or views. Defined by: CREATE ASSERTION name CHECK (condition); Condition may refer to any relation or attribute in the database schema. 2009-4-28 * Triggers: Motivation Assertions are powerful, but the DBMS often can’t tell when they need to be checked. Attribute- and tuple-based checks are checked at known times, but are not powerful. Triggers let the user decide when to check for any condition. 2009-4-28 * Event-Condition-Action Rules Another name for “trigger” is ECA rule, or event-condition-action (事件-条件-动作) rule. Event : typically a type of database modification, e.g., “insert on Sells.” Condition : Any SQL boolean-valued expression. Action : Any SQL statements. * Schemas定义了表结构. * 这里涉及到一些逻辑演算的含义 2009-4-28 * Weak Entity-Set Rules (2) The key for a weak entity set is its own underlined attributes and the keys for the supporting entity sets. E.g., (player) number and (team) name is a key for Players in the previous example. 2009-4-28 * From E/R Diagrams to Relations Entity set ? relation. Attributes ? attributes. Relationships ? relations whose attributes are only: The keys of the connected entity sets. Attributes of the relationship itself. 2009-4-28 * Handling Weak Entity Sets Relation for a weak entity set must include attributes for its complete key (including those belonging to other entity sets), as well as its own, nonkey attributes. A supporting relationship is redundant and yields no