E F Codd And Relational Theory A Detailed Review And Analysis Of Codd S Major Database Writings

E. F. Codd's relational model of data has been described as one of the three greatest inventions of all time (the other two being agriculture and the scientific method), and his receipt of the 1981 ACM Turing Award?the top award in computer science?for inventing it was thoroughly deserved. The papers in which Codd first described his model were staggering in their originality; they had, and continue to have, a huge impact on just about every aspect of the way we do business in the world today. And yet few people, even in the professional database community, are truly familiar with those papers. This book is an attempt to remedy this sorry state of affairs. In it, well known author C. J. Date provides a detailed examination of all of Codd's major technical publications, explaining the nature of his contribution in depth, and in particular highlighting not only the many things he got right but also some of the things he got wrong.

Along with its companion volume (Database Dreaming Volume II), this book offers a collection of essays on the general topic of relational databases and relational database technology. Most of those essays, though not all, have been published before, but only in journals and magazines that are now hard to find or in books that are now out of print. Here’s a lightly edited excerpt from the preface (so this is the author speaking): I went back and reviewed all of those early essays, looking for ones that seemed worth reviving (or, rather, revising and reviving) at this time. Of course, some of them definitely weren’t! However, out of a total of around 130 original papers, I did find some 20 or so that seemed to me worth preserving and hadn’t already been incorporated in, or superseded by, more recent books of mine. So I tracked down the original versions of those 20 or so papers and set to work. When I was done, though, I found I had somewhere in excess of 600 pages on my hands—too much, in my view, for just one book, and so I split them across two separate volumes. Highlights of the present volume include a discussion of the difficulties involved in providing a relational interface to a nonrelational system; a tutorial on the quantifiers and what happens to them under three-valued logic; an examination of the effect of user defined types on optimization; some thoughts on normalization and database design tools; and caveats regarding certain important database operators, especially outer join and negation.

Some things seem so obvious that they don’t need to be spelled out in detail. Or do they? In computing, at least (and probably in any discipline where accuracy and precision are important), it can be quite dangerous just to assume that some given concept is “obvious,” and indeed universally understood. Serious mistakes can happen that way! The first part of this book discusses features of the database field—equality, assignment, naming—where just such an assumption seems to have been made, and it describes some of the unfortunate mistakes that have occurred as a consequence. It also explains how and why the features in question aren’t quite as obvious as they might seem, and it offers some advice on how to work around the problems caused by assumptions to the contrary. Other parts of the book also deal with database issues where devoting some preliminary effort to spelling out exactly what the issues in question entailed could have led to much better interfaces and much more carefully designed languages. The issues discussed include redundancy and indeterminacy; persistence, encapsulation, and decapsulation; the ACID properties of transactions; and types vs. units of measure. Finally, the book also contains a detailed deconstruction of, and response to, various recent pronouncements from the database literature, all of them having to do with relational technology. Once again, the opinions expressed in those pronouncements might seem “obvious” to some people (to the writers at least, presumably), but the fact remains that they’re misleading at best, and in most cases just flat out wrong.

This book is a revised, upgraded, and hugely improved version of an earlier one called Logic and Databases. Although it’s effectively a brand new book, therefore, the following remarks from that earlier book are still relevant here. First, logic and databases are inextricably intertwined. The relational model itself is essentially just elementary logic, tailored to database needs. Now, if you’re a database professional, this won’t be news to you—but you still might not realize just how much everything we do in the database world is (or should be!) affected by logic. Logic is fundamental, and everywhere. As a database professional, therefore, you owe it to yourself to understand the basics of formal logic, and you ought to be able to explain (and perhaps defend) the connections between formal logic and database technology. And that’s what this book is about. What it does is show, through a series of partly independent, partly interrelated essays, just how various crucial aspects of database technology—some of them very familiar, others maybe less so—are solidly grounded in formal logic. Overall, the goal is to help you realize the importance of logic in everything you do, and also, I hope, to help you see that logic can be fun.

The Database Relational Model: A Retrospective Review and Analysis is a retrospective of E.F. Codd's original ideas in which C.J. Date revisits the original papers, highlights their critical contributions to the basis of relational database management systems, and discusses the current day applications of these ideas. Codd's relational model, first presented to the world in a series of research papers from 1969 to 1979, was at the time revolutionary. More than 30 years later, however, it seems that the database community in general has come to regard the relational model as somewhat passe and no longer relevant, even though the entire database industry is founded on that model. Two factors that might explain this are that several of Codd's original papers have since become hard to find, and some of his writings were somewhat difficult to read and understand. This book aims to clearly evaluate Codd's original ideas and relate them to today's database society.

All of today’s mainstream database products support the SQL language, and relational theory is what SQL is supposed to be based on. But are those products truly relational? Sadly, the answer is no. This book shows you what a real relational product would be like, and how and why it would be so much better than what’s currently available. With this unique book, you will: Learn how to see database systems as programming systems Get a careful, precise, and detailed definition of the relational model Explore a detailed analysis of SQL from a relational point of view There are literally hundreds of books on relational theory or the SQL language or both. But this one is different. First, nobody is more qualified than Chris Date to write such a book. He and Ted Codd, inventor of the relational model, were colleagues for many years, and Chris’s involvement with the technology goes back to the time of Codd’s first papers in 1969 and 1970. Second, most books try to use SQL as a vehicle for teaching relational theory, but this book deliberately takes the opposite approach. Its primary aim is to teach relational theory as such. Then it uses that theory as a vehicle for teaching SQL, showing in particular how that theory can help with the practical problem of using SQL correctly and productively. Any computer professional who wants to understand what relational systems are all about can benefit from this book. No prior knowledge of databases is assumed.