As much as I’d like to be able to produce completely error free books, the reality of the computer publishing industry is that the pace at which books must be written and released makes this very difficult. And regretfully, my own books do have sporadic mistakes and typos scattered throughout them.
For the benefit of my readers, here is a current errata for Certified ColdFusion Developer Study Guide. Feel free to print this page for future reference.
And as always, if you come across errors that I do not know about, please let me know. I’ll make sure they are added to this list, and will try to have them corrected in future reprints.
Original printing (400 pages, published March 23, 2001)
Page | Location | Correction |
---|---|---|
44 | First line of tip. | Should be: A query string is allowed at the end of the URL listed in the URL attribute. |
44 | Caution, fourth to last line. | Should be: </script>. |
46 | First paragraph beneath header “Reuse and Including Files”, 5th line. | “<CFINLCUDE>” should be “<CFINCLUDE>”. |
66 | SQL statement at top of page, final line of SQL code. | Should be: ORDER BY Breeding DESC. |
73 | Second tip, <CFPARAM> code examples. | First <CFPARAM> should be: <CFPARAM NAME=”FName” DEFAULT=”Emily”>. Second <CFPARAM> should be: <CFPARAM NAME=”URL.FName” DEFAULT=”Emily”>. |
92 | Code snippet in the middle of the page, first line, words “APPLICATION.States”. | Should be: APPLICATION.GetStates. |
93 | Line 3, word SESSION in “SESSION variables”. | Should be: SERVER. |
104 | Question 3. | Should be: Which cookie is set by ColdFusion application server only when the attribute SETDOMAINCOOKIES is set to yes in the <CFAPPLICATION> tag?. |
111 | Tip at top of page, fourth and fifth lines. | Should read: “moving from most specific (SESSION scope) to least specific (SERVER scope)”. |
111 | Tip at top of page, numbered list. | Items #1 and #3 are reversed, SESSION should be first and SERVER last. |
120 | First paragraph beneath “Special Lists”. | GetFunctionList() returns a structure and should not be listed here. |
129 | Code block at bottom of page, fourth <CFSET>. | Should be: <CFSET aFlightInfo[1][1][3]=”Springfield, MA”>. |
137 | Bulleted list at top of page (second line). | First item, “SERVER”, should not be listed. |
138 | Note, third line. | Word “down” should be “up”. |
138 | Code Example 2. | Line missing, insert “<CFSET aFlightInfo[2]=StructNew()>”> in between the third and fourth lines from the bottom. |
141 | First line, expression (between pound signs). | Should be: #qGetFlightData.destination[i]#. |
147 | Second to last comment in <CFSCRIPT> block at the bottom of the page. | Should be: // this line below runs only if x is neither 1 nor 2. |
149 | <CFSCRIPT> block at the bottom of the page, fifth line, words “WriteOutputWriteOutput;”. | Should be: WriteOutput(a);. |
150 | FOR-IN Statement code example, fifth line. | A line break is missing in between “to work” and “FOR (x”, the FOR statement should start a new line and is not part of the comment. |
150 | FOR-IN Statement, text before code snippet. | Third sentence is incorrect and should be deleted. |
150 | <CFSCRIPT> block at the top of the page, fifth line, words “WriteOutputWriteOutput;”. | Should be: WriteOutput(a);. |
150 | FOR-IN Statement code example, line five. | “fr” shoudl be “for”. |
162 | First line of note at top of page. | <CFPROCRESULT> should be <CFPROCPARAM>. |
166 | Second note, last line. | READ COMMITTED should be READ UNCOMMITTED. |
169 | Note, second to last line. | “<CFTRANSACTION/>” should be “</CFTRANSACTION>”. |
174 | Fifth line from bottom of the page, text PERF MONITOR. | Should be: PERF_MONITOR. |
174 | Line beginning “argument is” in final paragraph, words “PERF MONITOR”. | Should be: PERF_MONITOR. |
176 | Bulleted list of variables under “Show Variables”. | Last bullet should be “Cookies”. |
177 | Section entitled “Manual Debugging” first paragraph, third line. | Text “simple local variables” should not be there and should be deleted. |
187 | Code example beneath Table 21.7, <CFTHROW> tag. | Should read: <CFTHROW TYPE=”Reorder” MESSAGE=”Reorder product #ProdName#” EXTENDEDINFO=”#Now()#”>. |
188 | Second to last line, TEMPLATE value. | Should be “ExpressionTemplate.cfm”. |
237 | Third line of body text. | “<CFILE>” should be “<CFFILE>”. |
238 | Fourth paragraph starting with the word “MODE”, fourth line. | Should read: MODE=”755″ gives rwxr-xr-x permissions (owner=read/write/execute, group=read/execute, other=read/execute). |
239 | First tip, first word. | “<CFILE>” should be “<CFFILE>”. |
248 | Fifth line of Summary. | Word “<CFILE>” should be “<CFFILE”>. |
253 | Third line beneath “Publishing to Static Pages”, final words. | Should read: “can be instructed to save the”. |
257 | Second paragraph beneath “Sending Simple Text Email”. | First word should be: “<CFMAIL>”. |
287 | Second tip, second line. | Should read: “wildcards used at the start of a search pattern”. |
289 | Second SQL UPDATE example, second line. | Should read: “SET product_price=product_price+10”. |
293 | Second to last line on page. | “FORM” should be “FROM”. |
312 | Code example, fourth line. | Missing text “product_id=” after WHERE and before <CFQUERYPARAM>. |
316 | Second to last line on page. | “referred to be” should read: “referred to by”. |
320 | Question 1, answer A. | Should read: “VARIABLES”. |
346 | Chapter 5, answer 4. | Answer is missing the number “4.” in front of it. |
347 | Chapter 12, answer 2. | Correct answers are A and D. |
348 | Chapter 16, answer 1. | Opening words should read: “C. The other answers are valid”. |
349 | Chapter 17, answer 1, end of third line. | Should read: “Answer D is”. |
349 | Chapter 17, answer 1, third line. | “is rarely used for output” should read “is not only used for output”. |
350 | Chapter 19, answer 1, fourth line, first word. | Should be “UNCOMMITTED”. |
350 | Chapter 22, answer 2, third line. | “C:\Cfusion\Bin” should be “C:\CFusion\CustomTags”. |
352 | Chapter 32, answer 1. | Last sentence should read: “C is not a valid keyword.” |
353 | Chapter 36, answer 1, second line. | Word “VARIABLE” should be “VARIABLES”. |