Errata
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
| Version |
Location |
Description |
Submitted By |
| Printed |
Page 24
dealing with WHERE clause |
Not really an error, but a strong suggestion:
I found out a couple of months ago that 'WHERE operations' on text are case-INsensitive(*), unless you do some pretty confusing things that I've never quite gotten to work.
In a 545 page book about MySQL, seems like something people would want to know.
(*) e.g.
"select * from mytable where myname like 'John%';"
not only finds "JohnF" but also "johnf" and "JOHNF" and "JoHnF" - yuck!
|
Anonymous |
| Printed |
Page 24
dealing with WHERE clause |
sorry, not really an error, but a strong suggestion:
I found out to my horror a coupla months ago that 'WHERE operations' on text are case-INsensitive(*), unless you do some pretty confusing things that I've never quite gotten to work.
That was on the short list of three things I wanted your book to tell me, and if it is there I cannot find it.
In a 545 page book about MySQL, seems like something people would want to know :)
thanks!
(*) e.g.
"select * from mytable where myname like 'John%';"
not only finds "JohnF" but also "johnf" and "JOHNF" and "JoHnF" - yuck!
|
Anonymous |
| Printed |
Page 54
2/3 down the page |
Under the heading for SHA1(), the subheading says SHA(string). It should say SHA1(string).
|
Anonymous |
| Printed |
Page 54
2/3 down the page |
Under the heading for SHA1(), the subheading says SHA(string). It should say SHA1(string).
|
Anonymous |
| Printed |
Page 83
CREATE TABLE statement syntax specification |
Replace
[[AS] SELECT ...]
with
[[IGNORE|REPLACE][AS] SELECT ...]
The modifier affects behaviour when the statement considers rows
having a duplicate UNIQUE key: IGNORE retains the existing row and
discards the new one, while REPLACE overwrites the existing row.
Without the modifier duplicates cause an error.
Also needs an explanation in the text and an index entry.
|
Anonymous |
| Printed |
Page 150
Under the definition for MAX |
The definition for MAX should read "This function returns the highest number..." instead of "lowest number"
|
Anonymous |
