Errata

SQL Pocket Guide

Errata for SQL Pocket Guide

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 4
(Example file) mysql_sample_data.sql

The following command is rejected by MySQL 5.0.41 using phpMyAdmin 2.10.2. I'm running everything under MAMP on Mac.

create table dual (
dummy varchar(1)
);

Error text is vague, just says syntax error. I also tried adding engine=innodb, without success. Can't see how it differs substantially from the CREATE TABLE pivot command above it.

 Anonymous   
Printed Page 4
(Example file) mysql_sample_data.sql

The following command is rejected by MySQL 5.0.41 using phpMyAdmin 2.10.2. I'm running everything under MAMP on Mac.

create table dual (
dummy varchar(1)
);

Error text is vague, just says syntax error. I also tried adding engine=innodb, without success. Can't see how it differs substantially from the CREATE TABLE pivot command above it.

 Anonymous   
Printed Page 4
Second Paragraph

The sample data for MYSQL does not work. The table name 'dual' (line 146) cannot be created because 'dual' is a reserved word. Performing a find/replace on 'dual', changing it to 'duel' for example, fixes the problem.

 Anonymous   
Printed Page 8
Max precision/scale section

For Oracle the book gives a maximum precision of 38 and a maximum scale of 127. I believe the precision must always be greater than or equal to the scale.

 Anonymous   
Printed Page 8
Max precision/scale section

For Oracle the book gives a maximum precision of 38 and a maximum scale of 127. I believe the precision must always be greater than or equal to the scale.

 Anonymous   
Printed Page 24
End of table 3

Format should be yyyy-mm-ddThh:mm:ss.mmm

Sample string coming straight out of SQL Server is:
2012-06-04T17:37:20.720

 Anonymous  Jun 04, 2012 
Printed Page 52
3rd paragraph beginning with "In DB2, use either LOCATE or POSSTR

It says:

LOCATE(substring, string[, position])
POSSTR(substring, string) <- WRONG, arguments should be switched according to IBM:

POSSTR ->

http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000835.htm

and LOCATE -> http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000820.htm

have the arguments in different order and they work like that too, check:

select LOCATE('N', 'ONNO') from sysibm.sysdummy1; and
select POSSTR('ONNO', 'N') from sysibm.sysdummy1;

 Anonymous   
Printed Page 52
3rd paragraph beginning with "In DB2, use either LOCATE or POSSTR

It says:

LOCATE(substring, string[, position])
POSSTR(substring, string) <- WRONG, arguments should be switched according to IBM:

POSSTR ->

http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000835.htm

and LOCATE -> http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000820.htm

have the arguments in different order and they work like that too, check:

select LOCATE('N', 'ONNO') from sysibm.sysdummy1; and
select POSSTR('ONNO', 'N') from sysibm.sysdummy1;

 Anonymous   
Printed Page 85
3rd para

You wrote "... then it joins the table of months to upfall..."

I think you mean "years" rather than "months".

 Anonymous   
Printed Page 85
3rd para

You wrote "... then it joins the table of months to upfall..."

I think you mean "years" rather than "months".

 Anonymous   
Printed Page 102
Between Predicates

The example for BETWEEN is misleading. it is not <= to the higher value.

Correction: BETWEEN is >= first value and < the second.

 Anonymous   
Printed Page 102
Between Predicates

The example for BETWEEN is misleading. it is not <= to the higher value.

Correction: BETWEEN is >= first value and < the second.

 Anonymous