Foundation for Future Database Systems: The Third Manifesto / Edition 2

Hardcover (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $2.12
Usually ships in 1-2 business days
(Save 94%)
Other sellers (Hardcover)
  • All (12) from $2.12   
  • New (4) from $76.51   
  • Used (8) from $2.12   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$89.12
Seller since 2008

Feedback rating:

(210)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New

Ships from: Chicago, IL

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$76.51
Seller since 2015

Feedback rating:

(356)

Condition: New
Brand New Item.

Ships from: Chatham, NJ

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
$105.00
Seller since 2015

Feedback rating:

(228)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$105.00
Seller since 2015

Feedback rating:

(228)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Close
Sort by

Overview

A detailed study of the impact of objects and type theory on the relational model of data, including a comprehensive model of type inheritance!

"This book should be recommended reading for software engineers, database designers, graduate students, undergraduate students, data modelers--for just about anybody with a serious interest in database technology."
--Declan Brady, MBCS, Lead Systems Architect, ICL

"As a database application designer/architect, I'm interested in ideals as well as in currently available tools . . . This book is a rich source of worthy ideals. In particular, it provides good coverage of areas where SQL, and much commercial Object Orientation training material, are found lacking."
--Tom Pledger, Peace International Software

Foundation for Future Database Systems: The Third Manifesto is a proposal for the future direction of data and database management systems (DBMSs). It consists of a precise, formal definition of an abstract model of data, to be considered as a blueprint for the design of a DBMS and a database language. Among other things, it provides a rock-solid foundation for integrating relational and object technologies.

The proposed foundation represents an evolutionary step, not a revolutionary one; it builds on Codd's relational model of data and on the research that sprang from that work. It also incorporates a precise and comprehensive specification for a method of defining data types, including a comprehensive model of type inheritance, to address a lack that has been observed by many authorities; thus, it alsobuilds on research in the field of object orientation. With a sound footing in both camps of the object/relational divide, therefore, the Manifesto is offered as a firm foundation for the DBMSs of the future.

Significant features of this new edition include:

  • Major extensions to the inheritance model
  • Significantly improved language proposals
  • Improved discussions of read-only vs. update operators, selectors, THE_ operators, tuple types vs. possible representations, grouping and ungrouping, first normal form, assignment, constraints, predicates, and many other topics
  • All SQL discussions upgraded to the level of the new SQL:1999 standard
  • Several new appendixes




0201709287B04062001
Read More Show Less

Editorial Reviews

Booknews
Updates (1998). In this blueprint for the future direction of database management systems evolved from Codd's relational model of data, provides right and wrong approaches to building a DBMS, and no frills and detailed versions of the Manifesto. Appendices elaborate on such matters as the Two Great Blunders, changing semantics, comparisons with SQL and ODMG, and trends. Date is the author of (Addison-Wesley, 2000); Darwen works for IBM-UK. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Read More Show Less

Product Details

  • ISBN-13: 9780201709285
  • Publisher: Pearson Education
  • Publication date: 5/12/2000
  • Edition number: 2
  • Pages: 576
  • Product dimensions: 7.38 (w) x 9.22 (h) x 1.01 (d)

Read an Excerpt

PREFACE:

The Third Manifesto is a detailed proposal for the future direction of data and database management systems (DBMSs). Like Codd's original papers on the relational model, it can be seen as an abstract blueprint for the design of a DBMS and the language interface to such a DBMS. Among (many) other things, it lays the foundation for what we believe is the logically correct approach to integrating relational and object technologies--a topic of considerable interest at the present time, given the recent appearance in the marketplace of several "object/relational" DBMS products (sometimes called universal servers). Perhaps we should add immediately that we do not regard the idea of integrating relational and object technologies as "just another fad," soon to be replaced by some other briefly fashionable idea. On the contrary, we think that object/relational systems are in everyone's future--a fact that makes it even more important to get the logical foundation right, of course, while we still have time to do so.

The first version of the Manifesto was published informally in early 1994 (though we had been thinking about the idea of such a document for several years prior to that time), and the first "official" version appeared in 1995. Since then we have presented the material in a variety of forms and forums and discussed it with numerous people--indeed, we continue to do so to this day--and we have refined and expanded the original document many, many times. We would immediately like to stress, however, that those refinements and expansions have always been exactly that; nobody has ever shown us that we were completelyon the wrong track, and development of the Manifesto has always proceeded in an evolutionary, not a revolutionary, manner. Now we feel it is time to make the material available in some more permanent form; hence the present book.

One reason we feel the time is ripe for wider dissemination of our ideas is as follows. As already indicated, we see a parallel between the Manifesto and Codd's original papers on the relational model; like those papers of Codd's, the Manifesto offers a foundation for what (we believe) the database systems of the future ought to look like. Also like those papers of Codd's, however, the Manifesto itself is, deliberately, fairly terse and not all that easy to read or understand.* Would it not have been nice to have had a book that documented and explained and justified Codd's ideas, back at the beginning of the relational era? Well, here we are at the beginning of "the object/relational era," and--modesty aside--we believe this book can play a role analogous to that of that hypothetical relational book. To that end, we have been careful to include not only the formal specifications of the Manifesto itself (of course), but also a great deal of supporting and explanatory material and numerous detailed examples.

By the way, we should make it clear that our ideas do rest very firmly in the relational tradition. Indeed, we would like our Manifesto to be seen, in large part, as a definitive statement of just what the relational model itself consists of at the time of writing** (for it too has undergone a certain amount of evolution over the years). Despite our remarks in the previous paragraph concerning "the object/relational era," therefore, the ideas expressed in the Manifesto must not be thought of as superseding those of the relational model, nor do they do so; rather, they use those ideas as a foundation and build on them. We believe strongly that the relational model is still highly relevant to database theory and practice and will remain so for the foreseeable future. Thus, we regard our Manifesto as being very much in the spirit of Codd's original work and continuing along the path he originally laid down. To repeat, we are talking evolution, not revolution.

There is another point to be made here, too. Given the current interest in object/relational systems, we can expect to see a flurry of books on such systems over the next few years. However, it is unlikely, if history is anything to go by, that those books will concern themselves very much with general principles or underlying theory; it is much more probable that they will be product-oriented, if not actually product-specific. The present book, by contrast, definitely is concerned with theoretical foundations rather than products; in other words, it allows you to gain a solid understanding of the underlying technology per se, thereby enabling you among other things to approach the task of evaluating commercial products from a position of conceptual strength.

While we are on the subject of commercial products, incidentally, we should make it clear that we ourselves have no particular commercial ax to grind. We regard ourselves as independent so far as the marketplace is concerned, and we are not trying to sell any particular product.*** The ax we do have to grind is that of logical correctness!--we want to do our best to ensure that the industry goes down the right path, not the wrong one.

*As Bertrand Russell has it: "Writing can be either readable or precise, but not at the same time" (quoted by John Sowa in his book Conceptual Structures: Information Processing in Mind and Machine, Addison-Wesley, 1984).
**Indeed, we even toyed at one time with the idea of calling the book A Relational Model of Data for Large Shared Data Banks.
***It is true that one of us, Hugh Darwen, works for a company that does have a product to sell, but the product in question is not mentioned by name anywhere in this book.
And in that connection, we would like to mention another reason we feel the book is timely: namely, the fact that the SQL standards bodies, both national and international, are currently at work on a proposal called SQL3 that addresses some of the same issues as our Manifesto does. An appendix to the present book gives a detailed set of comparisons between our ideas and those of the current SQL3 proposal.*
*SQL3 was ratified in late 1999. Its official name is now SQL:1999--and we use this latter name in preference to "SQL3" throughout this new edition (though we usually abbreviate both names to just plain "SQL," unqualified). The version of the standard that was current prior to the ratification of SQL:1999 was known formally asSQL:1992.
What is more, another body, the Object Data Management Group (ODMG), has also published a set of proposals that, again, address some of the same issues. Another appendix to this book therefore takes a look at the ODMG ideas as well. Two more special features of the book are the following:
  • We define a new and simplified relational algebra, called A, which emphasizes rather more than previous algebras have done its firm foundation in predicate logic.
  • We also define a database programming language called Tutorial D, which realizes the ideas of the Manifesto in concrete form and is used as the basis for examples and illustrations throughout the book.

We would also like to mention one further feature that we believe to be highly significant, and that is our proposal for a model of subtyping and inheritance. Many authorities have rightly observed that there is currently no consensus on any such model, and we offer our proposal for consideration in the light of this observation. Indeed, we believe we have some original--and, we also believe, logically sound and correct--thoughts to offer on this important subject. Part IV of the book (five chapters) is devoted to this topic.

Structure of the Book

The body of the book is divided into four major parts:

I. Preliminaries
II. Formal Specifications
III. Informal Discussions and Explanations
IV. Subtyping and Inheritance

Part I sets the scene by explaining in general terms what the Manifesto is all about and why we wrote it. It also contains an informal overview of two approaches to building an object/relational system, one of which is (we claim) right and the other wrong. We recommend that you read both of these chapters fairly carefully before moving on to later parts of the book.

Part II is the most formal part. It consists of three chapters:

  • Chapter 3 is the Manifesto itself--a "no frills" version, with virtually nil by way of illustration or further explanation. (For the benefit of anyone who might have seen earlier drafts of the Manifesto, we should explain that this "no frills" version consists essentially of just the formal text from those earlier drafts, with all commentary and suchlike material deleted.)
  • Chapter 4 contains the definition, mentioned above, of our new relational algebra ("A").
  • Chapter 5 defines the language Tutorial D. This language, which is (of course) based on the principles laid down in the Manifesto and on our new algebra A, serves as the basis for examples throughout the remainder of the book. It also serves to suggest what a DBMS supporting the ideas of the Manifesto might look like in actual practice.

Note: Most of the material of these three chapters is provided primarily for purposes of reference; it is not necessary, and probably not even a good idea, to study it exhaustively, at least not on a first reading.

Part III is the real heart of the book. It consists of six chapters, one for each of the six sections of the Manifesto as defined in Part II. (Again, for the benefit of anyone who might have seen earlier drafts of the Manifesto, this part of the book consists essentially of a hugely expanded version of the informal commentary from those earlier drafts.) Each chapter discusses the relevant section of the Manifesto in considerable detail, with examples, and thereby explains the motivations and rationale behind the formal proposals of Part II (especially those in Chapter 3). Note, therefore, that the Manifesto itself serves as the organizing principle for this, the major part of the book.

Finally, Part IV does for subtyping and inheritance what Parts I, II, and III do for the Manifesto proper. It consists of five chapters. Chapter 12 gives an overall introduction to the topic; Chapter 13 gives formal definitions; and Chapters 14, 15, and 16 give informal explanations and discussions of the ideas underlying those formal definitions. To be more specific, Chapter 14 covers single inheritance and scalar types (only); Chapter 15 then extends the material of Chapter 14 to address multiple inheritance; finally, Chapter 16 then extends those ideas still further to take tuple and relation types into account as well.

In addition to the foregoing, there are also several appendixes: one defining an alternative version of Tutorial D that is based on relational calculus instead of relational algebra, another discussing "subtables and supertables," another containing the text of an interview the present authors gave on the subject of the Manifesto in 1994, and so on. In particular, the SQL and ODMG comparisons can be found in this part of the book, as already mentioned. The final appendix (Appendix K) gives an annotated and consolidated list of references for the entire book.

Note: While we are on the subject of references to publications, we should explain that throughout the book such references take the form of numbers in square brackets. For example, the reference "3" refers to the third item in the list of references in Appendix K, viz., a paper by Malcolm P. Atkinson and O. Peter Buneman entitled "Types and Persistence in Database Programming Languages," published in ACM Computing Surveys, Volume 19, No. 2, in June 1987.

Last, we should say a word about our use of terminology. It is our experience that many of the terms in widespread use in the database field, and other related fields, are subject to a variety of different interpretations, and that communication suffers badly as a result. Examples seem superfluous (you can surely provide plenty of your own). We have therefore found it necessary to introduce our own terminology in certain places in the book (though we have tried to keep such cases to a minimum, of course, and we have not intentionally used familiar terms in unfamiliar ways). We apologize if this fact should cause you any unnecessary difficulties.

Intended Readership

Who should read this book? Well, in at least one sense the book is definitely not self-contained--it does assume you are professionally interested in database technology and are therefore reasonably well acquainted with classical database theory and practice. However, we have tried to define and explain, as carefully as we could, any concepts that might be thought novel; in fact, we have done the same for several concepts that really should not be novel at all but do not seem to be as widely understood as they ought to be ("candidate key" is a case in point). Thus, we have tried to make the book suitable for both reference and tutorial purposes, and we have indicated clearly those portions of the book that are more formal in style and are provided primarily for reference.

Our intended audience is, therefore, just about anyone with a serious interest in database technology, including but not limited to the following:

  • Database language designers and standardizers;
  • DBMS product implementers and other vendor personnel;
  • Data and database administrators;
  • "Information modelers" and database designers;
  • Database application designers and implementers;
  • Computer science professors specializing in database issues;
  • Database students, both graduate and undergraduate;
  • People responsible for DBMS product evaluation and acquisition;
  • People interested in any aspect of the "objects vs. relations" controversy, including especially anyone who might be involved in object/relational systems;
  • People interested in type theory and the topic of type inheritance.

For academic readers in particular (students as well as teachers), we should add that what we have tried to do is present the foundations of the database field in a way that is clear, precise, correct, and uncluttered by the baggage--not to mention mistakes--that usually (and regrettably) seem to accompany commercial products. Thus, we believe the book provides an opportunity to acquire a firm understanding of that crucial foundation material, without being distracted by irrelevancies. Perhaps we should say too that we believe there are several interesting (and, we hope, self-evident) teaching and research projects lurking just below the surface of certain portions of the material.

Acknowledgments

First of all, we are delighted to be able to acknowledge all of the numerous friends and colleagues who, over the past several years, have given encouragement, participated in discussions, and offered comments (both written and oral) on various drafts of The Third Manifesto or portions thereof: John Andrews, Tanj Bennett, Charley Bontempo, Declan Brady, Bob Brown, Rick Cattell, Linda DeMichiel, Vincent Dupuis, Bryon Ehlmann, Mark Evans, Ron Fagin, Oris Friesen, Ric Gagliardi, Ray Gates, Mikhail Gilula, Zaid Holmin, Michael Jackson, Achim Jung, John Kneiling, Adrian Larner, Bruce Lindsay, David Livingstone, Albert Maier, Carl Mattocks, Nelson Mattos, David McGoveran, Roland Merrick, Serge Miranda, Jim Panttaja, Mary Panttaja, Fabian Pascal, Ron Ross, Arthur Ryman, Alan Sexton, Mike Sykes, Stephen Todd, Rick van der Lans, Anton Versteeg, and Fred Wright (and we apologize if we have inadvertently omitted anyone from this list). We would also like to acknowledge the many conference and seminar attendees, too numerous to mention individually, who have expressed support for the ideas contained herein.

Second, we would like to thank our reviewers Charley Bontempo, Declan Brady, Rick Cattell, David Livingstone, and David McGoveran for their careful and constructive comments on the manuscript.

Third, we are--of course!--deeply indebted to our wives, Lindy Date and Lindsay Darwen, for their unfailing support throughout this project and so many others over the years.

Finally, we are, as always, grateful to our editor, Elydia Davis, and to the staff at Addison-Wesley for their assistance and their continually high standards of professionalism. It has been, as always, a pleasure to work with them.

Hugh Darwen adds: My gratitude to my colleague and friend, Chris Date, goes without saying. However, I would like to comment on something, significant to us, that you possibly haven't noticed. It concerns the book's attribution. In our previous joint productions our names have been linked by the preposition with, intended to distinguish the primary author from the contributing assistant. This time around we have thought it more appropriate to use the conjunction and, of whose commutativity we Relationlanders are especially conscious! We came to this conclusion despite the fact that, as usual, Chris has done the lion's share of the actual writing. That the writing so faithfully and agreeably records our joint thinking (often painfully wrought out) is therefore a source of great pleasure to me, especially in those cases where I can still identify the thinking in question as having arisen from ideas first placed into discussion by myself.

My own thinking has been molded, of course, with the aid of many mentors over the years, including Chris himself. Here I would like to single out just two other people for special mention: Adrian Larner for my relational thinking, and Nelson Mattos for my object-oriented thinking.

Chris Date adds: If Hugh feels he has learned from me over the years, I can assure you (and him) that I have most certainly learned a great deal from him!--a state of affairs for which I will always be grateful. As for the matter of the book's attribution, it is of course true that The Third Manifesto is a joint effort, but Hugh should really take the credit for being the original and prime mover on this project: It was he who came up with the idea of the Manifesto in the first place, and it was he who wrote the very first draft, early in 1994. Though I should immediately add that our thinking on the matters with which the Manifesto deals goes back very much further than that; in some respects, in fact, I think we could claim that it goes all the way back to the beginning of our respective careers in the database field.

C. J. Date, Healdsburg, California
Hugh Darwen, Shrewley, England
1998 (revised 2000)


0201709287P04062001
Read More Show Less

Table of Contents

Preface.

PART I: PRELIMINARIES.

1. Background and Overview.
What Is The Third Manifesto?
Why Did We Write It?
Back to the Relational Future.
Some Guiding Principles.
Some Crucial Logical Differences.
Topics Deliberately Omitted.
The Third Manifesto: A Summary.

2. Objects and Relations.
Introduction.
What Problem Are We Trying to Solve?
Relations vs. Relvars.
Domains vs. Object Classes.
Relvars vs. Object Classes.
A Note on Inheritance.
Concluding Remarks.

PART II: FORMAL SPECIFICATIONS


3. The Third Manifesto.
RM Prescriptions.
RM Proscriptions.
OO Prescriptions.
OO Proscriptions.
RM Very Strong Suggestions.
OO Very Strong Suggestions.

4. A New Relational Algebra.
Introduction.
Motivation and Justification.
REMOVE, RENAME, and COMPOSE.
Treating Operators as Relations.
Formal Definitions.
Transitive Closure.

5. Tutorial D.
Introduction.
Types and Expressions.
Scalar Definitions.
Tuple Definitions.
Relational Definitions.
Scalar Operations.
Tuple Operations.
Relational Operations.
Relations and Arrays.
Statements.
Syntax Summary.
Mapping the Relational Operations.

PART III: INFORMAL DISCUSSIONS AND EXPLAINATIONS.


6. RM Prescriptions.
RM Prescription 1: Scalar Types.
RM Prescription 2: Scalar Values Are Typed.
RM Prescription 3: Scalar Operators.
RM Prescription 4: Actual vs. Possible Representations.
RM Prescription 5: Expose Possible Representations.
RM Prescription 6: Type Generator TUPLE.
RM Prescription 7: Type Generator RELATION.
RM Prescription 8: Equality.
RM Prescription 9: Tuples.
RM Prescription 10: Relations.
RM Prescription 11: Scalar Variables.
RM Prescription 12: Tuple Variables.
RM Prescription 13: Relation Variables (Relvars).
RM Prescription 14: Real vs. Virtual Relvars.
RM Prescription 15: Candidate Keys.
RM Prescription 16: Databases.
RM Prescription 17: Transactions.
RM Prescription 18: Relational Algebra.
RM Prescription 19: Relvar Names, Relation Selectors, and Recursion.
RM Prescription 20: Relation-Valued Operators.
RM Prescription 21: Assignments.
RM Prescription 22: Comparisons.
RM Prescription 23: Integrity Constraints.
RM Prescription 24: Relvar and Database Predicates.
RM Prescription 25: Catalog.
RM Prescription 26: Language Design.

7. RM Proscriptions.
RM Proscription 1: No Attribute Ordering.
RM Proscription 2: No Tuple Ordering.
RM Proscription 3: No Duplicate Tuples.
RM Proscription 4: No Nulls.
RM Proscription 5: No Nullological Mistakes.
RM Proscription 6: No Internal-Level Constructs.
RM Proscription 7: No Tuple-Level Operations.
RM Proscription 8: No Composite Attributes.
RM Proscription 9: No Domain Check Override.
RM Proscription 10: Not SQL.

8. OO Prescriptions.
OO Prescription 1: Compile-Time Type Checking.
OO Prescription 2: Type Inheritance (Conditional).
OO Prescription 3: Computational Completeness.
OO Prescription 4: Explicit Transaction Boundaries.
OO Prescription 5: Nested Transactions.
OO Prescription 6: Aggregate Operators and Empty Sets.

9. OO Proscriptions.
OO Proscription 1: Relvars Are Not Domains.
OO Proscription 2: No Object Ids.

10. RM Very Strong Suggestions.
RM Very Strong Suggestion 1: System Keys.
RM Very Strong Suggestion 2: Foreign Keys.
RM Very Strong Suggestion 3: Candidate Key Inference.
RM Very Strong Suggestion 4: Transition Constraints.
RM Very Strong Suggestion 5: Quota Queries.
RM Very Strong Suggestion 6: Generalized Transitive Closure.
RM Very Strong Suggestion 7: User-Defined Generic Operators.
RM Very Strong Suggestion 8: Special ("Default") Values.
RM Very Strong Suggestion 9: SQL Migration.

11. OO Very Strong Suggestions.
OO Very Strong Suggestion 1: Type Inheritance.
OO Very Strong Suggestion 2: Types and Operators Unbundled.
OO Very Strong Suggestion 3: Collection Type Generators.
OO Very Strong Suggestion 4: Conversion To/From Relations.
OO Very Strong Suggestion 5: Single-Level Store.

PART IV: SUBTYPING AND INHERITANCE.


12. Preliminaries.
Introduction.
Toward a Type Inheritance Model.
Single vs. Multiple Inheritance.
Scalars, Tuples, and Relations.
Summary.

13. The Inheritance Model.
Introduction.
IM Prescriptions.

14. Single Inheritance with Scalar Types.
Introduction.
IM Prescription 1: Types Are Sets.
IM Prescription 2: Subtypes Are Subsets.
IM Prescription 3: "Subtype Of" Is Reflexive.
IM Prescription 4: Proper Subtypes.
IM Prescription 5: "Subtype Of" Is Transitive.
IM Prescription 6: Immediate Subtypes.
IM Prescription 7: Types Disjoint Unless One a Subtype of the Other.
IM Prescription 8: Scalar Values with Inheritance.
IM Prescription 9: Scalar Variables with Inheritance.
IM Prescription 10: Specialization by Constraint.
IM Prescription 11: Assignment with Inheritance.
IM Prescription 12: Equality Etc. with Inheritance.
IM Prescription 13: Join Etc. with Inheritance.
IM Prescription 14: TREAT DOWN.
IM Prescription 15: Type Testing.
IM Prescription 16: Read-Only Operator Inheritance and Value Substitutability.
IM Prescription 17: Operator Signatures.
IM Prescription 18: Read-Only Parameters to Update Operators.
IM Prescription 19: Update Operator Inheritance and Variable Substitutability.
IM Prescription 20: Union, Dummy, and Maximal and Minimal Types.

15. Multiple Inheritance with Scalar Types.
Introduction.
The Running Example.
IM Prescriptions 1-20 Revisited.
Least Specific Types Unique.
Most Specific Types Unique.
Type Testing with Multiple Inheritance.
Remarks on Operator Inheritance.

16. Inheritance with Tuple and Relation Types.
Introduction.
IM Prescription 21: Tuple/Relation Subtypes and Supertypes.
IM Prescriptions 1-20 Still Apply.
IM Prescription 22: Tuple/Relation Values with Inheritance.
IM Prescription 23: Maximal and Minimal Tuple/Relation Types.
IM Prescription 24: Tuple/Relation Most Specific Types.
IM Prescription 25: Tuple/Relation Variables with Inheritance.
Specialization by Constraint.
Tuple/Relation Assignment with Inheritance.
Tuple/Relation Equality Etc. with Inheritance.
Tuple/Relation TREAT DOWN.
Tuple/Relation Type Testing.
The Additional Prescriptions Summarized.

APPENDIXES.


Appendix A. A Relational Calculus Version of Tutorial D.
Introduction.
Boolean Expressions.
Builtin Relation Operator Invocations.
Free and Bound Range Variable References.
Relation UPDATE and DELETE Operators.
Examples.

Appendix B. The Two Great Blunders.
Introduction.
The First Great Blunder.
The Second Great Blunder.

Appendix C. A Design Dilemma?
Introduction.
Encapsulation.
Discussion.
Further Considerations.

Appendix D. Types and Units.
Introduction.
Type Definition.
Selectors.
THE_ Operators.
Computational Operators.
Display Operators.
Type Constraints.
A More Complex Example.

Appendix E. Subtables and Supertables.
Introduction.
Some General Observations.
The Terminology Is Extremely Bad.
The Concept Is Not Type Inheritance.
Why?

Appendix F. More on Changing Semantics and Related Matters.
Introduction.
Analysis.
A Solution.
Another Example.

Appendix G. Specialization By Constraint and Related Matters.
Introduction.
The 3 Out of 4 "Rule."
What Does Inheritance Really Mean?
Benefits of S by C.
Is a Colored Circle a Circle?
Object Ids Undermine Inheritance.
Why the Problem Does Not Arise with Foreign Keys.

Appendix H. A Comparison with SQL.
Introduction.
RM Prescriptions.
RM Proscriptions.
OO Prescriptions.
OO Proscriptions.
RM Very Strong Suggestions.
OO Very Strong Suggestions.
IM Prescriptions.
History of the Wrong Equation in SQL.

Appendix I. A Comparison with ODMG.
Introduction.
Overview.
RM Prescriptions.
RM Proscriptions.
OO Prescriptions.
OO Proscriptions.
RM Very Strong Suggestions.
OO Very Strong Suggestions.
IM Prescriptions.

Appendix J. The Next 25 Years of the Relational Model?
Remarks on Republication.
Introduction.
Background.
The Third Manifesto and SQL.
Technical Content.
More on SQL.
Miscellaneous Questions.

Appendix K. References and Bibliography.
Index.
Read More Show Less

Preface

The Third Manifesto is a detailed proposal for the future direction of data and database management systems (DBMSs). Like Codd's original papers on the relational model, it can be seen as an abstract blueprint for the design of a DBMS and the language interface to such a DBMS. Among (many) other things, it lays the foundation for what we believe is the logically correct approach to integrating relational and object technologies--a topic of considerable interest at the present time, given the recent appearance in the marketplace of several "object/relational" DBMS products (sometimes called universal servers). Perhaps we should add immediately that we do not regard the idea of integrating relational and object technologies as "just another fad," soon to be replaced by some other briefly fashionable idea. On the contrary, we think that object/relational systems are in everyone's future--a fact that makes it even more important to get the logical foundation right, of course, while we still have time to do so.

The first version of the Manifesto was published informally in early 1994 (though we had been thinking about the idea of such a document for several years prior to that time), and the first "official" version appeared in 1995. Since then we have presented the material in a variety of forms and forums and discussed it with numerous people--indeed, we continue to do so to this day--and we have refined and expanded the original document many, many times. We would immediately like to stress, however, that those refinements and expansions have always been exactly that; nobody has ever shown us that we were completely on the wrongtrack, and development of the Manifesto has always proceeded in an evolutionary, not a revolutionary, manner. Now we feel it is time to make the material available in some more permanent form; hence the present book.

One reason we feel the time is ripe for wider dissemination of our ideas is as follows. As already indicated, we see a parallel between the Manifesto and Codd's original papers on the relational model; like those papers of Codd's, the Manifesto offers a foundation for what (we believe) the database systems of the future ought to look like. Also like those papers of Codd's, however, the Manifesto itself is, deliberately, fairly terse and not all that easy to read or understand.* Would it not have been nice to have had a book that documented and explained and justified Codd's ideas, back at the beginning of the relational era? Well, here we are at the beginning of "the object/relational era," and--modesty aside--we believe this book can play a role analogous to that of that hypothetical relational book. To that end, we have been careful to include not only the formal specifications of the Manifesto itself (of course), but also a great deal of supporting and explanatory material and numerous detailed examples.

By the way, we should make it clear that our ideas do rest very firmly in the relational tradition. Indeed, we would like our Manifesto to be seen, in large part, as a definitive statement of just what the relational model itself consists of at the time of writing** (for it too has undergone a certain amount of evolution over the years). Despite our remarks in the previous paragraph concerning "the object/relational era," therefore, the ideas expressed in the Manifesto must not be thought of as superseding those of the relational model, nor do they do so; rather, they use those ideas as a foundation and build on them. We believe strongly that the relational model is still highly relevant to database theory and practice and will remain so for the foreseeable future. Thus, we regard our Manifesto as being very much in the spirit of Codd's original work and continuing along the path he originally laid down. To repeat, we are talking evolution, not revolution.

There is another point to be made here, too. Given the current interest in object/relational systems, we can expect to see a flurry of books on such systems over the next few years. However, it is unlikely, if history is anything to go by, that those books will concern themselves very much with general principles or underlying theory; it is much more probable that they will be product-oriented, if not actually product-specific. The present book, by contrast, definitely is concerned with theoretical foundations rather than products; in other words, it allows you to gain a solid understanding of the underlying technology per se, thereby enabling you among other things to approach the task of evaluating commercial products from a position of conceptual strength.

While we are on the subject of commercial products, incidentally, we should make it clear that we ourselves have no particular commercial ax to grind. We regard ourselves as independent so far as the marketplace is concerned, and we are not trying to sell any particular product.*** The ax we do have to grind is that of logical correctness!--we want to do our best to ensure that the industry goes down the right path, not the wrong one.

*As Bertrand Russell has it: "Writing can be either readable or precise, but not at the same time" (quoted by John Sowa in his book Conceptual Structures: Information Processing in Mind and Machine, Addison-Wesley, 1984).
**Indeed, we even toyed at one time with the idea of calling the book A Relational Model of Data for Large Shared Data Banks.
***It is true that one of us, Hugh Darwen, works for a company that does have a product to sell, but the product in question is not mentioned by name anywhere in this book.

And in that connection, we would like to mention another reason we feel the book is timely: namely, the fact that the SQL standards bodies, both national and international, are currently at work on a proposal called SQL3 that addresses some of the same issues as our Manifesto does. An appendix to the present book gives a detailed set of comparisons between our ideas and those of the current SQL3 proposal.*

*SQL3 was ratified in late 1999. Its official name is now SQL:1999--and we use this latter name in preference to "SQL3" throughout this new edition (though we usually abbreviate both names to just plain "SQL," unqualified). The version of the standard that was current prior to the ratification of SQL:1999 was known formally asSQL:1992.

What is more, another body, the Object Data Management Group (ODMG), has also published a set of proposals that, again, address some of the same issues. Another appendix to this book therefore takes a look at the ODMG ideas as well. Two more special features of the book are the following:

  • We define a new and simplified relational algebra, called A, which emphasizes rather more than previous algebras have done its firm foundation in predicate logic.
  • We also define a database programming language called Tutorial D, which realizes the ideas of the Manifesto in concrete form and is used as the basis for examples and illustrations throughout the book.

We would also like to mention one further feature that we believe to be highly significant, and that is our proposal for a model of subtyping and inheritance. Many authorities have rightly observed that there is currently no consensus on any such model, and we offer our proposal for consideration in the light of this observation. Indeed, we believe we have some original--and, we also believe, logically sound and correct--thoughts to offer on this important subject. Part IV of the book (five chapters) is devoted to this topic.

Structure of the Book

The body of the book is divided into four major parts:

I. Preliminaries
II. Formal Specifications
III. Informal Discussions and Explanations
IV. Subtyping and Inheritance

Part I sets the scene by explaining in general terms what the Manifesto is all about and why we wrote it. It also contains an informal overview of two approaches to building an object/relational system, one of which is (we claim) right and the other wrong. We recommend that you read both of these chapters fairly carefully before moving on to later parts of the book.

Part II is the most formal part. It consists of three chapters:

  • Chapter 3 is the Manifesto itself--a "no frills" version, with virtually nil by way of illustration or further explanation. (For the benefit of anyone who might have seen earlier drafts of the Manifesto, we should explain that this "no frills" version consists essentially of just the formal text from those earlier drafts, with all commentary and suchlike material deleted.)
  • Chapter 4 contains the definition, mentioned above, of our new relational algebra ("A").
  • Chapter 5 defines the language Tutorial D. This language, which is (of course) based on the principles laid down in the Manifesto and on our new algebra A, serves as the basis for examples throughout the remainder of the book. It also serves to suggest what a DBMS supporting the ideas of the Manifesto might look like in actual practice.

Note: Most of the material of these three chapters is provided primarily for purposes of reference; it is not necessary, and probably not even a good idea, to study it exhaustively, at least not on a first reading.

Part III is the real heart of the book. It consists of six chapters, one for each of the six sections of the Manifesto as defined in Part II. (Again, for the benefit of anyone who might have seen earlier drafts of the Manifesto, this part of the book consists essentially of a hugely expanded version of the informal commentary from those earlier drafts.) Each chapter discusses the relevant section of the Manifesto in considerable detail, with examples, and thereby explains the motivations and rationale behind the formal proposals of Part II (especially those in Chapter 3). Note, therefore, that the Manifesto itself serves as the organizing principle for this, the major part of the book.

Finally, Part IV does for subtyping and inheritance what Parts I, II, and III do for the Manifesto proper. It consists of five chapters. Chapter 12 gives an overall introduction to the topic; Chapter 13 gives formal definitions; and Chapters 14, 15, and 16 give informal explanations and discussions of the ideas underlying those formal definitions. To be more specific, Chapter 14 covers single inheritance and scalar types (only); Chapter 15 then extends the material of Chapter 14 to address multiple inheritance; finally, Chapter 16 then extends those ideas still further to take tuple and relation types into account as well.

In addition to the foregoing, there are also several appendixes: one defining an alternative version of Tutorial D that is based on relational calculus instead of relational algebra, another discussing "subtables and supertables," another containing the text of an interview the present authors gave on the subject of the Manifesto in 1994, and so on. In particular, the SQL and ODMG comparisons can be found in this part of the book, as already mentioned. The final appendix (Appendix K) gives an annotated and consolidated list of references for the entire book.

Note: While we are on the subject of references to publications, we should explain that throughout the book such references take the form of numbers in square brackets. For example, the reference "3" refers to the third item in the list of references in Appendix K, viz., a paper by Malcolm P. Atkinson and O. Peter Buneman entitled "Types and Persistence in Database Programming Languages," published in ACM Computing Surveys, Volume 19, No. 2, in June 1987.

Last, we should say a word about our use of terminology. It is our experience that many of the terms in widespread use in the database field, and other related fields, are subject to a variety of different interpretations, and that communication suffers badly as a result. Examples seem superfluous (you can surely provide plenty of your own). We have therefore found it necessary to introduce our own terminology in certain places in the book (though we have tried to keep such cases to a minimum, of course, and we have not intentionally used familiar terms in unfamiliar ways). We apologize if this fact should cause you any unnecessary difficulties.

Intended Readership

Who should read this book? Well, in at least one sense the book is definitely not self-contained--it does assume you are professionally interested in database technology and are therefore reasonably well acquainted with classical database theory and practice. However, we have tried to define and explain, as carefully as we could, any concepts that might be thought novel; in fact, we have done the same for several concepts that really should not be novel at all but do not seem to be as widely understood as they ought to be ("candidate key" is a case in point). Thus, we have tried to make the book suitable for both reference and tutorial purposes, and we have indicated clearly those portions of the book that are more formal in style and are provided primarily for reference.

Our intended audience is, therefore, just about anyone with a serious interest in database technology, including but not limited to the following:

  • Database language designers and standardizers;
  • DBMS product implementers and other vendor personnel;
  • Data and database administrators;
  • "Information modelers" and database designers;
  • Database application designers and implementers;
  • Computer science professors specializing in database issues;
  • Database students, both graduate and undergraduate;
  • People responsible for DBMS product evaluation and acquisition;
  • People interested in any aspect of the "objects vs. relations" controversy, including especially anyone who might be involved in object/relational systems;
  • People interested in type theory and the topic of type inheritance.

For academic readers in particular (students as well as teachers), we should add that what we have tried to do is present the foundations of the database field in a way that is clear, precise, correct, and uncluttered by the baggage--not to mention mistakes--that usually (and regrettably) seem to accompany commercial products. Thus, we believe the book provides an opportunity to acquire a firm understanding of that crucial foundation material, without being distracted by irrelevancies. Perhaps we should say too that we believe there are several interesting (and, we hope, self-evident) teaching and research projects lurking just below the surface of certain portions of the material.

Acknowledgments

First of all, we are delighted to be able to acknowledge all of the numerous friends and colleagues who, over the past several years, have given encouragement, participated in discussions, and offered comments (both written and oral) on various drafts of The Third Manifesto or portions thereof: John Andrews, Tanj Bennett, Charley Bontempo, Declan Brady, Bob Brown, Rick Cattell, Linda DeMichiel, Vincent Dupuis, Bryon Ehlmann, Mark Evans, Ron Fagin, Oris Friesen, Ric Gagliardi, Ray Gates, Mikhail Gilula, Zaid Holmin, Michael Jackson, Achim Jung, John Kneiling, Adrian Larner, Bruce Lindsay, David Livingstone, Albert Maier, Carl Mattocks, Nelson Mattos, David McGoveran, Roland Merrick, Serge Miranda, Jim Panttaja, Mary Panttaja, Fabian Pascal, Ron Ross, Arthur Ryman, Alan Sexton, Mike Sykes, Stephen Todd, Rick van der Lans, Anton Versteeg, and Fred Wright (and we apologize if we have inadvertently omitted anyone from this list). We would also like to acknowledge the many conference and seminar attendees, too numerous to mention individually, who have expressed support for the ideas contained herein.

Second, we would like to thank our reviewers Charley Bontempo, Declan Brady, Rick Cattell, David Livingstone, and David McGoveran for their careful and constructive comments on the manuscript.

Third, we are--of course!--deeply indebted to our wives, Lindy Date and Lindsay Darwen, for their unfailing support throughout this project and so many others over the years.

Finally, we are, as always, grateful to our editor, Elydia Davis, and to the staff at Addison-Wesley for their assistance and their continually high standards of professionalism. It has been, as always, a pleasure to work with them.

Hugh Darwen adds: My gratitude to my colleague and friend, Chris Date, goes without saying. However, I would like to comment on something, significant to us, that you possibly haven't noticed. It concerns the book's attribution. In our previous joint productions our names have been linked by the preposition with, intended to distinguish the primary author from the contributing assistant. This time around we have thought it more appropriate to use the conjunction and, of whose commutativity we Relationlanders are especially conscious! We came to this conclusion despite the fact that, as usual, Chris has done the lion's share of the actual writing. That the writing so faithfully and agreeably records our joint thinking (often painfully wrought out) is therefore a source of great pleasure to me, especially in those cases where I can still identify the thinking in question as having arisen from ideas first placed into discussion by myself.

My own thinking has been molded, of course, with the aid of many mentors over the years, including Chris himself. Here I would like to single out just two other people for special mention: Adrian Larner for my relational thinking, and Nelson Mattos for my object-oriented thinking.

Chris Date adds: If Hugh feels he has learned from me over the years, I can assure you (and him) that I have most certainly learned a great deal from him!--a state of affairs for which I will always be grateful. As for the matter of the book's attribution, it is of course true that The Third Manifesto is a joint effort, but Hugh should really take the credit for being the original and prime mover on this project: It was he who came up with the idea of the Manifesto in the first place, and it was he who wrote the very first draft, early in 1994. Though I should immediately add that our thinking on the matters with which the Manifesto deals goes back very much further than that; in some respects, in fact, I think we could claim that it goes all the way back to the beginning of our respective careers in the database field.

C. J. Date, Healdsburg, California
Hugh Darwen, Shrewley, England
1998 (revised 2000)

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)