BIBLIO is the largest independent book marketplace in the world, with over 100 million books.

Skip to content

Database Technology: Nulls Considered Harmful

Database Technology: Nulls Considered Harmful

Database Technology: Nulls Considered Harmful
Stock photo: cover may vary

Database Technology: Nulls Considered Harmful Paperback - 2024

by Chris Date

Add to wish list
  • Used
New

Description

like new.
Ask the seller a question Add to wish list
A$177.53
A$5.85 Delivery within USA
Standard delivery: 2 to 14 days
More delivery options
Ships from GreatBookPrices (Maryland, United States)
The BIBLIO Guarantee

Details

  • Title Database Technology: Nulls Considered Harmful
  • Author Chris Date
  • Binding Paperback
  • Condition New
  • Pages 246
  • Volumes 1
  • Language ENG
  • Publisher Technics Publications
  • Publication date 2024-07-08
  • Bookseller's Inventory # 47992273
  • ISBN 9781634624763 / 1634624769
  • Weight 0.95 lbs (0.43 kg)
  • Dimensions 9.25 x 7.5 x 0.52 in (23.50 x 19.05 x 1.32 cm)
  • Category Computers - Data Base Management
  • Quantity available 5

About GreatBookPrices Maryland, United States

Biblio member since 2024

Since 1991, we have worked every day to serve our customers with state-of-the-art technology and world class service. We are dedicated to providing customers around the world with the widest selection of books, DVDs, and CDs at the absolute lowest price.

Terms of Sale: 30 day return guarantee, with full refund including original shipping costs for up to 30 days after delivery if an item arrives misdescribed or damaged.

Browse books from GreatBookPrices

Reader reviews for Database Technology: Nulls Considered Harmful

Write a review for this book

There are no reviews for this book yet. Be the first to write a review!

Your review will be anonymous unless you login or create an account first.

Overall rating
Remember: You’re rating the book as a work, not the seller or the condition of the specific copy you purchased!

Important Terms and Guidelines

  • Please focus on the book’s content and context. Also, add any personal comments as to how you enjoyed the book. Substantiate your likes and dislikes. You may make comparisons to other books.
  • Reviews must be at least 140 characters in length.
  • Please do not reveal critical plot elements.
  • This is not a help line. Contact customer support if you need help.
Your review must not include:
  • Obscenities, discriminatory language, or other insulting language not suitable for public domain
  • Advertisements, “spam” content, or references to other products, offers or websites.
  • Email addresses, URLs, phone numbers, physical addresses or other contact information.
  • Overly critical comments about other reviews or reviewers
  • Time-sensitive material (i.e. promotional tours, seminars, lectures, etc.)
  • Availability, price, or alternative ordering/shipping information

From the publisher

Essentially all truly general purpose database systems today are based on the relational model of data. That model was invented by E. F. ("Ted") Codd in the late 1960s and early 1970s, during his employment at the IBM Research Laboratory in San Jose, California, and it was solidly based on conventional two-valued logic, 2VL. Unfortunately, those same general purpose database systems today all use the language SQL as their user language-and SQL is based not on 2VL but on what's called three-valued logic, 3VL, instead, and uses what are called nulls to represent missing information. In fact, Codd himself subsequently extended his original model to support 3VL and nulls as well. (Actually, basing SQL on 3VL and adding 3VL to the relational model seem to have occurred in lockstep, as it were. Certainly both developments occurred at the same place-the IBM San Jose Research Laboratory-at more or less the same time.)


But 3VL is a disastrously bad basis on which to build databases, or database applications, or database languages.It's bad because 3VL doesn't behave the way reality behaves, which means that results that 3VL says are correct are often not correct in the real world. Not only that, but SQL's implementation of 3VL is itself incorrect in places, which means it effectively adds another layer of wrong answers on top of the first. Bottom line:


If you have nulls in your database, you're getting wrong answers.


This book explains this issue in detail. It also contains numerous practical suggestions for dealing with the problem.

Please wait a moment while we load the requested page.

tracking-