SQL and Relational Theory: How to Write Accurate SQL Code
Par :Formats :
Définitivement indisponible
Cet article ne peut plus être commandé sur notre site (ouvrage épuisé ou plus commercialisé). Il se peut néanmoins que l'éditeur imprime une nouvelle édition de cet ouvrage à l'avenir. Nous vous invitons donc à revenir périodiquement sur notre site.
Disponible dans votre compte client Decitre ou Furet du Nord dès validation de votre commande. Le format Multi-format est :
- Pour les liseuses autres que Vivlio, vous devez utiliser le logiciel Adobe Digital Edition. Non compatible avec la lecture sur les liseuses Kindle, Remarkable et Sony
, qui est-ce ?Notre partenaire de plateforme de lecture numérique où vous retrouverez l'ensemble de vos ebooks gratuitement
Pour en savoir plus sur nos ebooks, consultez notre aide en ligne ici
C'est si simple ! Lisez votre ebook avec l'app Vivlio sur votre tablette, mobile ou ordinateur :
- Nombre de pages432
- FormatMulti-format
- ISBN978-0-596-80093-2
- EAN9780596800932
- Date de parution23/01/2009
- Protection num.NC
- Infos supplémentairesMulti-format incluant PDF sans p...
- ÉditeurO'Reilly
Résumé
Understanding SQL's underlying theory is the best way to guarantee that your SQL code is correct and your database schema is robust and maintainable. On the other hand, if you're not well versed in the theory, you can fall into several traps. In SQL and Relational Theory, author C. J. Date demonstrates how you can apply relational theory directly to your use of SQL. With numerous examples and clear explanations of the reasoning behind them, you'll learn how to deal with common SQL dilemmas, such as:
- Should database access granted be through views instead of base tables?
- Nulls in your database are causing you to get wrong answers.
Why? What can you do about it? - Could you write an SQL query to find employees who have never been in the same department for more than six months at a time? - SQL supports "quantified comparisons, " but they're better avoided. Why? How do you avoid them? - Constraints are crucially important, but most SQL products don't support them properly. What can you do to resolve this situation? Database theory and practice have evolved since Edgar Codd originally defined the relational model back in 1969.
Independent of any SQL products, SQL and Relational Theory draws on decades of research to present the most up-to-date treatment of the material available anywhere. Anyone with a modest to advanced background in SQL will benefit from the many insights in this book.
Why? What can you do about it? - Could you write an SQL query to find employees who have never been in the same department for more than six months at a time? - SQL supports "quantified comparisons, " but they're better avoided. Why? How do you avoid them? - Constraints are crucially important, but most SQL products don't support them properly. What can you do to resolve this situation? Database theory and practice have evolved since Edgar Codd originally defined the relational model back in 1969.
Independent of any SQL products, SQL and Relational Theory draws on decades of research to present the most up-to-date treatment of the material available anywhere. Anyone with a modest to advanced background in SQL will benefit from the many insights in this book.
Understanding SQL's underlying theory is the best way to guarantee that your SQL code is correct and your database schema is robust and maintainable. On the other hand, if you're not well versed in the theory, you can fall into several traps. In SQL and Relational Theory, author C. J. Date demonstrates how you can apply relational theory directly to your use of SQL. With numerous examples and clear explanations of the reasoning behind them, you'll learn how to deal with common SQL dilemmas, such as:
- Should database access granted be through views instead of base tables?
- Nulls in your database are causing you to get wrong answers.
Why? What can you do about it? - Could you write an SQL query to find employees who have never been in the same department for more than six months at a time? - SQL supports "quantified comparisons, " but they're better avoided. Why? How do you avoid them? - Constraints are crucially important, but most SQL products don't support them properly. What can you do to resolve this situation? Database theory and practice have evolved since Edgar Codd originally defined the relational model back in 1969.
Independent of any SQL products, SQL and Relational Theory draws on decades of research to present the most up-to-date treatment of the material available anywhere. Anyone with a modest to advanced background in SQL will benefit from the many insights in this book.
Why? What can you do about it? - Could you write an SQL query to find employees who have never been in the same department for more than six months at a time? - SQL supports "quantified comparisons, " but they're better avoided. Why? How do you avoid them? - Constraints are crucially important, but most SQL products don't support them properly. What can you do to resolve this situation? Database theory and practice have evolved since Edgar Codd originally defined the relational model back in 1969.
Independent of any SQL products, SQL and Relational Theory draws on decades of research to present the most up-to-date treatment of the material available anywhere. Anyone with a modest to advanced background in SQL will benefit from the many insights in this book.
