Å·±¦ÓéÀÖ

Volodymyr's Reviews > SQL and Relational Theory: How to Write Accurate SQL Code

SQL and Relational Theory by C.J. Date
Rate this book
Clear rating

by
4913869
's review

liked it
bookshelves: programming-cs, read-2016

Reader have to be very attentive to grasp some useful information about relational theory and how use it to write SQL. Endless purist`s lament about imperfection of the real world. Author criticizes the problems of existing RDBMS and SQL only from position of 100% relational theory compliance and never considers other factors which influenced these implementations. With all due respect to author`s contribution into relational theory his views on physical DB implementation are rather mythical and strange.
Even if considering this book as a pure SQL critique � it is still terribly written, like it never been edited: killing sentences structure, endless footnotes by author himself to explain what did he mean. and parts like extensive explanation of predicate logic.
� flag

Sign into Å·±¦ÓéÀÖ to see if any of your friends have read SQL and Relational Theory.
Sign In »

Reading Progress

February 8, 2011 – Shelved
July 29, 2015 – Shelved as: programming-cs
July 2, 2016 – Started Reading
July 2, 2016 – Shelved as: to-read
July 22, 2016 – Finished Reading
July 25, 2016 – Shelved as: read-2016

Comments Showing 1-1 of 1 (1 new)

dateUp arrow    newest »

Volodymyr Vladimir Galkin "In today’s SQL systems, application
program access to the database is provided either through a call level interface or through
an embedded, but conceptually distinct, data sublanguage ('embedded SQL'). But
embedded SQL is really just a call level interface with a superficial dusting of syntactic sugar, so the two approaches come to the same thing from the DBMS’s point of view, and indeed from the host language’s point of view as well. In other words, the DBMS and the host language are typically only loosely coupled in most systems today. As a result, much of the advantage of using a well designed, well structured programming language is lost in today’s database environment. Here’s a quote: 'Most programming errors in database
applications would show up as type errors [if the database definition were] part of the type
structure of the program.'"


back to top