Errata

SQL and Relational Theory

Errata for SQL and Relational Theory

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 29
middle of the page

WHERE NOT EXISTS
( SELECT *
FROM SP
WHERE SP.PNO = S.SNO )

should be

WHERE NOT EXISTS
( SELECT *
FROM S, SP
WHERE SP.PNO = S.SNO )

 Anonymous  Jul 12, 2009 
Printed Page 46
2nd paragraph on the page

In the book 'SQL and Relational Theory, 1st Edition', in section '2.8.
Collations in SQL', the third paragraph has been added in error.
(it's actually the 2nd paragraph on page 46)

 Anonymous  Jan 30, 2009 
PDF Page 46
2nd paragraph

The following lines (2nd "paragraph" on the page) should be removed:

So much for the basic idea. Then those two strings are clearly distinct, and yet they?re con-
sidered to ?compare equal? if PAD Space applies. R

 David O'Brennan  Sep 24, 2011 
Printed Page 73
3. SQL expression

The result of the third SQL expression should be "P1 * 9, P2 * 3" instead of "P1 * 9, P2 * 4".

Please note that tables P and SP contains 4 and 3 rows respectively (See figure 4-1).

Original expression:

3. SELECT P.PNO
FROM P, SP
WHERE ( SP. SNO = ' S1' AND
SP. PNO = P. PNO )
OR P. PNAME = ' Screw'

Result: P1 * 9, P2 * 4.

 Thomas Uhren  Jun 11, 2010 
Printed Page 74
8. SQL expression

The list of SQL formulations for the given query contains two identical SQL formulations (1. and 8.).

8. SELECT P. PNO
FROM P
WHERE P. PNAME = ' Screw'
OR P. PNO IN
( SELECT SP. PNO
FROM SP
WHERE SP. SNO = ' S1' )

1 . SELECT P.PNO
FROM P
WHERE P. PNAME = ' Screw'
OR P. PNO IN
( SELECT SP. PNO
FROM SP
WHERE SP. SNO = ' S1' )

This and the wrong result for one SQL formulation (Please see the errata for page 73) results in eleven (not twelve) different formulations and eight (not nine) different results - different, that is, with respect to their degree of duplication.

 Thomas Uhren  Jun 11, 2010 
Printed Page 78
4th paragraph - just one example. The web form forced a single page number.

The tiny asterisks for indicating the reference point in the text for footnotes were hard for my 60 year old eyes to pick up. The daggers for a second foot notes were clear. I've been using a yellow highlighter to mark the asterisks. Many of the notes make little sense unless placed in context by the text reference.

The book is fine: useful and informative.

 Lloyd Kvam  Sep 04, 2009 
Printed Page 345
Solution to Exercise 6.9.h)

The SQL-query returns a wrong result in the border case that there is no supplier located in London and there is a product without shipment (both at the same time). The SELECT DISTINCT should be just a SELECT from the table P.

   Apr 15, 2009 
Printed Page 348
Solution to Exercise 7.1.b)

Solution does not match exercise (roles of S and P were switched in exercise b) in comparison to exercise a), but NOT in the solution)

   Apr 18, 2009 
Printed Page 387
Last paragraph

The answer to the exercise B-24-b (page 312) is "False" and not "True" as stated in the ANSWERS TO EXERCISES section (page 387).

Anonymous  May 18, 2009 
Printed Page 394
lines 1 and 2

A closing parenthesis and the word "as" need to be added to the following sentence: "called object/relational features (see reference [28])), but they're mostly irrelevant as far as the goal of using SQL relationally is concerned."

 Anonymous  Jun 24, 2009 
Printed Page 399
Entry for Faroult, St?phane

The entry should read "Faroult, St?phane" NOT "Faroult, Stp?hane".

 Anonymous  Jun 24, 2009