Free Ebook SQL and Relational Theory: How to Write Accurate SQL Code
By soft data of guide SQL And Relational Theory: How To Write Accurate SQL Code to review, you might not need to bring the thick prints almost everywhere you go. At any time you have going to read SQL And Relational Theory: How To Write Accurate SQL Code, you can open your device to review this book SQL And Relational Theory: How To Write Accurate SQL Code in soft documents system. So easy as well as rapid! Reading the soft documents publication SQL And Relational Theory: How To Write Accurate SQL Code will certainly give you simple method to check out. It could additionally be quicker considering that you could review your e-book SQL And Relational Theory: How To Write Accurate SQL Code everywhere you really want. This on the internet SQL And Relational Theory: How To Write Accurate SQL Code can be a referred publication that you could enjoy the option of life.
SQL and Relational Theory: How to Write Accurate SQL Code
Free Ebook SQL and Relational Theory: How to Write Accurate SQL Code
Invest your time even for just few mins to read a book SQL And Relational Theory: How To Write Accurate SQL Code Reading an e-book will certainly never lower as well as squander your time to be ineffective. Reviewing, for some folks become a requirement that is to do each day such as hanging out for eating. Now, what concerning you? Do you prefer to read an e-book? Now, we will certainly show you a new e-book qualified SQL And Relational Theory: How To Write Accurate SQL Code that could be a brand-new way to discover the expertise. When reviewing this publication, you can get something to constantly keep in mind in every reading time, even pointer by action.
As known, book SQL And Relational Theory: How To Write Accurate SQL Code is popular as the window to open up the globe, the life, and also brand-new thing. This is just what the people currently require so much. Even there are many people that don't such as reading; it can be a selection as referral. When you really require the methods to develop the following motivations, book SQL And Relational Theory: How To Write Accurate SQL Code will truly guide you to the method. Additionally this SQL And Relational Theory: How To Write Accurate SQL Code, you will have no remorse to obtain it.
And now, after understanding the writer, you can also conquer that the book is recommended to review primarily develop the reasons. The presented book qualified SQL And Relational Theory: How To Write Accurate SQL Code is done to manage you in obtaining even more features of the lifestyle. You might not need to make different methods of related resources to take place. When you have the various means to read something, you can attempt to choose the soft data systems of this publication.
After obtaining the amazing opportunity of guide here, you could not disregard that SQL And Relational Theory: How To Write Accurate SQL Code becomes one of the books that you will certainly select. But, you might not take guide currently because of some troubles. When you're truly certain regarding the lesson and also impression obtained from this publication, you have to begin checking out asap. It is just what that makes you constantly feel amazing as well as astonished when understanding a brand-new lessons regarding a book.
About the Author
C.J. Date has a stature that is unique within the database industry. C.J. is a prolific writer, and is well-known for his best-selling textbook: An Introduction to Database Systems (Addison Wesley). C.J. is an exceptionally clear-thinking writer who can lay out principles and theory in a way easily understood by his audience.
Read more
Product details
Paperback: 582 pages
Publisher: O'Reilly Media; 3 edition (November 16, 2015)
Language: English
ISBN-10: 1491941170
ISBN-13: 978-1491941171
Product Dimensions:
7 x 1.2 x 9.2 inches
Shipping Weight: 2 pounds (View shipping rates and policies)
Average Customer Review:
2.7 out of 5 stars
6 customer reviews
Amazon Best Sellers Rank:
#282,371 in Books (See Top 100 in Books)
Executive summary: The subtitle is a canard. This book is not about SQL - it's about the author's view of an alternative universe that doesn't involve SQL. From p. 484 "The message of this book can be summed up: Let's implement the relational model!" - meaning, as the author will emphasize repeatedly, that SQL does not. I elaborate at length here to counter some 2nd edition reviews as well as comments in other O'Reilly books and on SO - reviews and comments that led me to lose $40 on this paperweight. I interpreted the book's description here as well as those reviews to mean the book would be primarily concerned with improved techniques for using SQL to accomplish more difficult tasks. But the function of SQL in this book is that of an anti-pattern. This book:a) Describes with excruciating repetitive detail the author's definition of "Relational Math" and its application to relational databases (RDBs).b) Advertises, illustrates, discusses, and promotes the author's home-brewed "Tutorial" language as a proper (in the author's estimation) implementation of the item a) concepts. Quoting p. 488 "we hope that Tutorial D ... will become the database language of choice ...". Another reviewer here has already identified this Trojan Horse feature.c) Criticizes, assails, lampoons, disparages, and complains about the SQL standard and its generally available implementations. Numerous complaints are asinine, such as one on p. 454 bemoaning the fact SQL prohibits defining a (index) key that references no columns.An incidental goal of the book appears to be promotion of the author as a crowd-acknowledged 'expert' whose every thought on RDBs is treasured. This rapidly became very annoying, exacerbated by the writing tenor and style, which is not that of a textbook, but more like multiple blog posts organized into chapters. Just one example, on p. 81: "Is this a tuple?", followed by a line drawing of a single-row table with heading and data. The author answers "Well no, it isn't - it's a picture of a tuple.", proceeding to pontificate about the difference. This exchange is, I suppose, intended to show the reader to be a dupe and the author to be ever so clever. If I ask you "Is that your dog?" and you reply "No, that's a picture of my dog." I will not consider you very clever, but rather more akin to a donkey's derriere. None of my college professors engaged in such a stunt - we would have hissed him off the platform. In a similar pedantic vein, an entire ch. explains what data types are - as if the reader has no programming experience - and complains bitterly about the lack of user-definable types and strict type-checking in SQL. Another ch. wails about the existence and use of nulls, advising (therefore) that many SQL features - such as OUTER JOINs should never be used (p. 125). Ch. 10 discusses at length various logical structures, many of which are not available in SQL. Ch. 12 purports to show how to properly implement relational expressions in SQL, with many example statements using correlated subqueries - up to 4 deep (meaning O^4 execution time), p. 429. Horrors. A 4pp. Appendix summarizes the "SQL recommendations" from the entire book - primarily a list of "Do not use / or do ..." followed by commonly used SQL features.Beyond the above short-list of defects, the following observations - had I known about them - would have prevented the loss of the $40 from my estate:a) There are no 3rd-party endorsements in the book - not a single college instructor, DBMS practitioner, book reviewer, etc. - zero.b) An enormous amount of space (>60%?) is devoted to examples, explanation, accolades, and discussion of the home-brewed "Tutorial" language, the reader's familiarity with same being totally useless in the real world since we are using some variant of SQL, not the home-brewed language.c) The bio page for the author lists no commercial accomplishments (software products?, professorships?, development team leaderships?) aside from selling books. Perhaps I am out-of-order in seeking them - this page informs us that the author "enjoys a reputation that is second to none".d) Appendix G, "Suggestions for Further Reading" contains 64 entries, 60% of them papers and books credited to the author.e) There is no case history, or even a single example line from a commercial application, illustrating the application of the book's recommendations and the consequent benefits. Further demonstrating the detachment from real world requirements, the claim is made (p. 306) that RDB performance enhancement is of no concern - that such enhancement can lead to loss of data integrity as well as RDB un-reliability. No real-world examples of these occurrences are given.After wading through this book cover-to-cover (sans the Exercises) and enduring all the ranting and puerile introspection (p. 336: "I apologize for the sloppy manner of speaking ... " and on it goes for several pages), I came away with very nearly nothing that would be useful in the day-to-day application of SQL. If you really want this book, check with the guy who bought mine on eBay - he may have it for sale already.
the author is ruining his book by constantly pushing is adgenda on you. Half of the code examples are written in the language "tutorial D" to show you how much more cool is this language vs SQL . you waste an enormous amount of time in dealing with 2 syntaxes . As much as I appreciate the author insight in some subject, you wonder if he is more interested in speaking about his "manifesto" or in helping you to write proper SQL.
I love how meticulous he is about framing and the logic that guides the theory. I wish everybody who is interested in data science or business analysis had this approach to understanding their fields.
right to the point with many examples. good book!
Its kind of hard to read the professor bless his heart for showing enthusiasm but it takes a lot of will power to get through the whole thing. There is a few diagrams i really liked though.
The worst textbook I've ever used. It does make a few good points and has a few interesting things to say, particularly about logic and how to apply it to databases. Mostly, it's inconsistent and difficult to read. I've learned a lot from figuring out exactly how he was wrong in his statements and more from trying to figure out what he was talking about, like with his comments on the prenex normal form which he briefly discusses and then refers over to an out of print journal where he might have explained it better. Overall, it's like reading an argument on facebook about databases, except there's only one guy arguing.
SQL and Relational Theory: How to Write Accurate SQL Code PDF
SQL and Relational Theory: How to Write Accurate SQL Code EPub
SQL and Relational Theory: How to Write Accurate SQL Code Doc
SQL and Relational Theory: How to Write Accurate SQL Code iBooks
SQL and Relational Theory: How to Write Accurate SQL Code rtf
SQL and Relational Theory: How to Write Accurate SQL Code Mobipocket
SQL and Relational Theory: How to Write Accurate SQL Code Kindle
0 komentar:
Posting Komentar