book

SQL and Relational Theory, 3rd Edition

by C.J. Date

November 2015

Intermediate to advanced

582 pages

16h 19m

English

O'Reilly Media, Inc.

Read now

Unlock full access

The relational model is much misunderstoodSome remarks on terminologyPrinciples not productsA review of the original modelModel vs. implementationProperties of relationsBase vs. derived relationsRelations vs. relvarsValues vs. variablesConcluding remarksExercisesAnswers

Types and relationsEquality comparisonsData value atomicityWhat’s a type?Scalar vs. nonscalar typesScalar types in SQLType checking and coercion in SQLCollations in SQLRow and table types in SQLConcluding remarksExercisesAnswers
What’s a tuple?Rows in SQLWhat’s a relation?Relations and their bodiesRelations are n-dimensionalRelational comparisonsTABLE_DUM and TABLE_DEETables in SQLColumn naming in SQLConcluding remarksExercisesAnswers
What’s wrong with duplicates?Duplicates: further issuesAvoiding duplicates in SQLWhat’s wrong with nulls?Avoiding nulls in SQLA remark on outer joinConcluding remarksExercisesAnswers
Updating is set levelRelational assignmentMore on candidate keysMore on foreign keysRelvars and predicatesRelations vs. typesExercisesAnswers
Some preliminariesMore on closureRestrictionProjectionJoinUnion, intersection, and differenceWhich operators are primitive?Formulating expressions one step at a timeWhat do relational expressions mean?Evaluating SQL table expressionsExpression transformationThe reliance on attribute namesExercisesAnswers
Exclusive unionSemijoin and semidifferenceExtendImage relationsDivideAggregate operatorsImage relations revisitedSummarizationSummarization revisitedGroup, ungroup, and relation valued attributes“What if” queriesA note on recursionWhat about ORDER BY?ExercisesAnswers
Type constraintsType constraints in SQLDatabase constraintsDatabase constraints in SQLTransactionsWhy database constraint checking must be immediateBut doesn’t some checking have to be deferred?Constraints and predicatesMiscellaneous issuesExercisesAnswers
Views are relvarsViews and predicatesRetrieval operationsViews and constraintsUpdate operationsWhat are views for?Views and snapshotsExercisesAnswers
Why do we need logic?Simple and compound propositionsSimple and compound predicatesQuantificationRelational calculusMore on quantificationSome equivalencesConcluding remarksExercisesAnswers
Some transformation lawsExample 1: Logical implicationExample 2: Universal quantificationExample 3: Implication and universal quantificationExample 4: Correlated subqueriesExample 5: Naming subexpressionsExample 6: More on naming subexpressionsExample 7: Dealing with ambiguityExample 8: Using COUNTExample 9: Another variationExample 10: UNIQUE quantificationExample 11: ALL or ANY comparisonsExample 12: GROUP BY and HAVINGExercisesAnswers
SELECT *Explicit tablesDot qualificationRange variablesSubqueries“Possibly nondeterministic” expressionsEmpty setsA simplified BNF grammarExercisesAnswers
The relational model vs. othersThe significance of theoryThe relational model definedDatabase variablesObjectives of the relational modelSome database principlesWhat remains to be done?
Vertical decompositionHorizontal decompositionWhat do the shaded entries mean?ConstraintsQueriesMore on predicatesExercisesAnswers
Functional segmentationShardingEventual consistencyThe Fernandez interview

Content preview from SQL and Relational Theory, 3rd Edition

Appendix B

SQL Departures from the Relational Model

Between the idea

And the reality ...

Falls the Shadow

—T. S. Eliot: The Hollow Men (1925)

In this appendix I summarize, mainly for purposes of reference and with little by way of additional commentary, some of the ways in which SQL—by which I mean, as always in this book, the standard version of that language, except where otherwise noted—departs from the relational model. Now, I know there are those who will quibble over specific items in what follows; it’s not easy to compile a list of this kind, especially if it’s meant to be orthogonal (i.e., if an attempt is made to keep the various items all independent of one another). But I don’t think such quibbling is important. What’s important is the cumulative effect, which quite frankly I think is overwhelming.¹

SQL fails to distinguish adequately between table values and table variables.
SQL tables aren’t the same as relations (or relvars), because they either permit or require, as the case may be:
1. Duplicate rows
2. Nulls
3. Left to right column ordering
4. Anonymous columns
5. Duplicate column names
6. Pointers
7. Hidden columns (at least in some products, though not in the standard as such)
Note that all of these differences constitute violations of The Information Principle (see Appendix A).
SQL has no proper table literals.
SQL often seems to think views aren’t tables.
SQL tables—views included!—must have at least one column (no support for TABLE_DEE and TABLE_DUM).
SQL has no support for ...