数据库库系统实现(二)课件.ppt

数据元素的表示;主要内容;Principles of Data Layout;Overview;作业;作业;作业;Boolean e.g., TRUE FALSE;Dates, e.g.: Integer: # days since Jan 1, 1900 8 chars: YYYYMMDD 7 chars: YYYYDDD 10 chars: YYYY-MM-DD (SQL2) (not YYMMDD! Why?) Time, e.g. Integer: seconds since midnight chars: HH:MM:SS[.FF…] (SQL2) ;String of characters Null terminated e.g., - Length given e.g., - Fixed length;Record - Collection of related fields;A SCHEMA (not record) contains following information - number of fields - type of each field - order in record - meaning of each field;Example: fixed format and length;Record itself contains format; “Self Describing”;Variable format useful for:;EXAMPLE: var format record with repeating fields Employee ? one or more children;Variant between FIXED/VAR format;Many variations in internal organization of record;模式信息主要为出现在CREATE TABLE语句中的信息； 关系的属性 属性类型 属性在元组中出现的顺序 属性或关系自身上的约束;SQL Server 数据行结构;Next: placing records into blocks;(1) separating records (2) spanned vs. unspanned (3) mixed record types – clustering (4) split records (5) sequencing (6) addressing records;Block (a) fixed size recs. - no need to separate (b) special marker (c) give record lengths (or offsets) - within each record - in block header (see later) ;Unspanned: records are within one block block 1 block 2 ... Spanned: records span block boundaries block 1 block 2 ...;Unspanned is much simpler, but may waste space… Spanned necessary if record size block size (e.g., fields containing large BLOBs for, say, MPEG video clips);Example (of unspanned records);Mixed - records of different types (e.g. DEPT, EMPLOYEE) allowed in same block e.g., a block: ; Records that are frequently accessed together should be in the same block;Example;If Q1 frequent, clustering is good But consider Q2: SELECT * FROM DEPT If Q2 is frequent, clustering is counter- productive; Fixed part in