Errata
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 |
---|---|---|---|---|
Page v Preface, 2nd Paragraph |
Typo on: |
H?ctor Cer?n Figueroa (@Telematica) | May 04, 2012 | |
Page v 2nd paragraph, 1st line, |
"yeras" instead of "years" |
KraigWalker | Sep 26, 2013 | |
ePub | Page 11 section: Freeform document format para 2, sentence 1 |
enfore instead of enforce |
Julian | Mar 12, 2014 |
Page 41 First code block, line 11 |
Line: "map": "function(doc) { for(i=0;i<doc.keywords.lenghth();i++) |
Cameron Grout | May 05, 2012 | |
Page 41 2nd paragraph code sample |
The JSON sample contains commas that are not followed by subsequent items. Example: |
Jenny Dybedahl | Aug 27, 2013 | |
Page 42,44 4th Paragraph |
At page 42 it's said that the design document id is "_design/recipes": |
aMec | Aug 05, 2012 | |
Page 48 4th Paragraph ("Accessing a view...") |
"The update doesn?t need or use the *update*." |
aMec | Aug 05, 2012 | |
Page 49 6th paragraph ("To do a range...") |
"If we add the UTF-8 character 007F to ?Apricot?, the range will only include recipes with the title starting with Apricot, even if the document ID contains other characters." |
aMec | Aug 05, 2012 |