没有合适的资源?快使用搜索试试~ 我知道了~
首页数据库系统导论 答案 第八版 C. J. Date An Introduction to Database Systems 8th
资源详情
资源评论
资源推荐

Copyright (c) 2003 C. J. Date page fm.1
╔════════════════════════════════════════════════════════════════╗
║ ║
║ I N S T R U C T O R ' S M A N U A L ║
║ ║
╚════════════════════════════════════════════════════════════════╝
f o r
╔════════════════════════════════════════════════════════════════╗
║ ║
║ A n I n t r o d u c t i o n ║
║ ║
║ t o ║
║ ║
║ D a t a b a s e S y s t e m s ║
║ ║
║ ║
║ ───── ♦♦♦♦♦ ─────
║
║ ║
║ ║
║ Eighth Edition ║
║ ║
╚════════════════════════════════════════════════════════════════╝
by
C. J. Date

Copyright (c) 2003 C. J. Date page fm.2
P r e f a c e
General Remarks
The purpose of this manual is to give guidance on how to use the
eighth edition of the book An Introduction to Database
Systems──referred to throughout the manual as simply "the book,"
or "this book," or "the present book," or just "the eighth
edition"──as a basis for teaching a database course. The book is
suitable for a primary (one- or two-semester) course at the junior
or senior undergraduate or first-year graduate level; it also
contains some more forward-looking and research-oriented material
that would be relevant to a more advanced course. Students are
expected to have a basic understanding of (a) the storage and file
management capabilities (indexing, hashing, etc.) of a modern
computer system, and (b) the features of a typical high-level
programming language (Java, Pascal, C, PL/I, etc.).
Let me immediately say a little more regarding these two
prerequisites:
1. In connection with the first, please note that although the
book proper contains nothing on the subject, there's an online
appendix available──Appendix D, "Storage Structures and Access
Methods──that does provide a tutorial overview of such
matters. That appendix is an upgraded version of material
that was included in the book proper in the first six
editions. But file management isn't specific to database
systems; what's more, it's a huge subject in its own right,
and it has textbooks of its own──see, e.g., File Organization
for Database Design, by Gio Wiederhold, published by McGraw-
Hill in 1987 (which, despite the title, is really about files,
not databases). That's why I've dropped the inline coverage
of such material from the last two editions of the present
book.
2. In connection with the second, please note that the book uses
a hypothetical language called Tutorial D as a basis for
examples throughout. Tutorial D might be characterized,
loosely, as a Pascal-like language; it's defined in detail in
reference [3.3]. (See the subsection immediately following
for an explanation of this reference format. I'll have more
to say regarding reference [3.3] in particular later in these
introductory notes──see the subsection on The Third Manifesto,
pages 6-8.)
All of that being said, I want to say too that I don't think
either of these prerequisites is particularly demanding; but you
should be prepared, as an instructor, to sidetrack occasionally

Copyright (c) 2003 C. J. Date page fm.3
and give a brief explanation of (e.g.) what indexes are all about,
if the question arises.
A note on style: The book itself follows convention in being
written in the first person plural (we, our, etc.). This manual,
by contrast, is written in the first person singular (I, my,
etc.)──except where (a) it quotes directly from the book, or (b)
it reflects ideas, opinions, positions, etc., that are due to both
Hugh Darwen and myself (again, see the subsection on The Third
Manifesto, pages 6-8). The latter case applies particularly to
Chapter 20 on type inheritance, Chapter 23 on temporal databases,
and Chapter 26 on object/relational databases.
The manual is also a little chattier than the book, using
elisions such as "it's" and "they're" instead of the more stilted
"it is" and "they are," etc.
Structure of the Book
The book overall consists of a preface plus 27 chapters (divided
into six parts), together with four appendixes, as follows:
Part I : Preliminaries
1. An Overview of Database Management
2. Database System Architecture
3. An Introduction to Relational Databases
4. An Introduction to SQL
Part II : The Relational Model
5. Types
6. Relations
7. Relational Algebra
8. Relational Calculus
9. Integrity
10. Views
Part III : Database Design
11. Functional Dependencies
12. Further Normalization I: 1NF, 2NF, 3NF, BCNF
13. Further Normalization II: Higher Normal Forms
14. Semantic Modeling
Part IV : Transaction Management
15. Recovery
16. Concurrency

Copyright (c) 2003 C. J. Date page fm.4
Part V : Further Topics
17. Security
18. Optimization
19. Missing Information
20. Type Inheritance
21. Distributed Databases
22. Decision Support
23. Temporal Databases
24. Logic-Based Databases
Part VI : Objects, Relations, and XML
25. Object Databases
26. Object/Relational Databases
27. The World Wide Web and XML
Appendixes
A. The TransRelational
tm
Model
B. SQL Expressions
C. Abbreviations, Acronyms, and Symbols
D. Storage Structures and Access Methods (online only)
The preface gives more specifics regarding the contents of each
part, chapter, etc. It also summarizes the major differences
between this eighth edition and its immediate predecessor.
By the way, if you're familiar with earlier editions, I'd like
to stress the point that this edition, like each of its
predecessors, is in large degree a brand new book──not least
because (of course) I keep learning myself and improving my own
understanding, and producing a new edition allows me to correct
past mistakes. (In this connection, I'd like to draw your
attention to the wonderful quote from Bertrand Russell in the
book's preface. Also please note the epigraphs by George
Santayana and Maurice Wilkes! It would be nice if the computer
science community would take these remarks to heart.)
The following notes, also from the book's preface, are lightly
edited here:
(Begin quote)
The book overall is meant to be read in sequence more or less as
written, but you can skip later chapters, and later sections
within chapters, if you choose. A suggested plan for a first
reading would be:
• Read Chapters 1 and 2 "once over lightly."

Copyright (c) 2003 C. J. Date page fm.5
• Read Chapters 3 and 4 very carefully.
• Read Chapters 5, 6, 7, 9, and 10 carefully, but skip Chapter
8──except, probably, for Section 8.6 on SQL (in fact, you
might want to treat portions of Section 8.6 "early," perhaps
along with the discussion of embedded SQL in Chapter 4).
Note: It would be possible to skip or skim Chapter 5, too,
but if you do you'll need to come back and deal with it
properly before you cover Chapter 20 or Chapters 25-27.
• Read Chapter 11 "once over lightly."
• Read Chapters 12 and 14 carefully, but skip Chapter 13. (You
could also read Chapter 14 earlier if you like, possibly right
after Chapter 4. Many instructors like to treat the
entity/relationship material much earlier than I do. For that
reason I've tried to make Chapter 14 more or less self-
contained, so that it can be read "early" if you like.)
• Read Chapters 15 and 16 carefully.
• Read subsequent chapters selectively (but in sequence),
according to taste and interest.
I'd like to add that instructors, at least, should read the
preface too (most people don't!).
Each chapter opens with an introduction and closes with a
summary; each chapter also includes a set of exercises (and the
online answers often give additional information about the subject
at hand). Each chapter also includes a set of references, many of
them annotated. This structure allows the subject matter to be
treated in a multi-level fashion, with the most important concepts
and results being presented inline in the main body of the text
and various subsidiary issues and more complex aspects being
deferred to the exercises, or answers, or reference annotation, as
appropriate.
With regard to those references, by the way, I should explain
that references are identified in the text by two-part numbers in
square brackets. For example, the reference "[3.1]" refers to the
first item in the list of references at the end of Chapter 3:
namely, a paper by E. F. Codd published in CACM 25, No. 2, in
February, 1982. (For an explanation of abbreviations used in
references──e.g., "CACM"──see Appendix B. Regarding Codd in
particular, let me draw your attention to the dedication in this
new edition of the book. It's a sad comment on the state of our
field that I often encounter database students or professionals
who have never heard of Ted Codd.)
剩余400页未读,继续阅读












安全验证
文档复制为VIP权益,开通VIP直接复制

评论10