Oracle PL/SQL Language Pocket Reference

Errata for Oracle PL/SQL Language Pocket Reference

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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 20
1st paragraph

The syntax statement for a variable declaration: variable_name datatype [ CONSTANT ] .... NOW READS: variable_name [ CONSTANT ] datatype ....

Anonymous    May 01, 2006
Printed
Page 20
1st paragraph

The syntax statement for a variable declaration: variable_name datatype [ CONSTANT ] .... NOW READS: variable_name [ CONSTANT ] datatype ....

Anonymous    May 01, 2006
Printed
Page 49
Paragraph beginning "Formal Parameters are..."

3rd sentence in paragraph says: "... the actual parameters to the procedure are in_id...", and should say: "... the formal parameters to the procedure are in_id..." Similarly, the 4th sentence in the paragraph says: "The formal parameters used in the call..." and should say: "The actual parameters used in the call..." The two terms "actual parameter" and "formal parameter" were defined in the same paragraph, and their sense is reversed in the two sentences above.

Anonymous    Oct 01, 2006
Printed
Page 49
Paragraph beginning "Formal Parameters are..."

3rd sentence in paragraph says: "... the actual parameters to the procedure are in_id...", and should say: "... the formal parameters to the procedure are in_id..." Similarly, the 4th sentence in the paragraph says: "The formal parameters used in the call..." and should say: "The actual parameters used in the call..." The two terms "actual parameter" and "formal parameter" were defined in the same paragraph, and their sense is reversed in the two sentences above.

Anonymous    Oct 01, 2006
Printed
Page 55
2nd line of code example from top of page

The code as written reads

Note from the Author or Editor:
Bottom of page 59 in 4th edition. This should be changed.

Suzanne Michelle  Aug 03, 2009 
Printed
Page 65
in the sample code the two lines following the "BEGIN"

The example code had the following lines BEGIN PIPE ROW(dad_in); -- identify stream input PIPE ROW(mom_in); -- identify stream input This was completely wrong. The PIPE ROW function only pipes output and not input. If these two PIPE ROW lines are removed then and only this is the example correct. AUTHOR'S REPLY: The example NOW READS: CREATE OR REPLACE TYPE num_tab_typ AS TABLE OF NUMBER / CREATE OR REPLACE FUNCTION piped_func(factor IN NUMBER) RETURN num_tab_typ PIPELINED AS BEGIN FOR counter IN 1..1000 LOOP PIPE ROW(counter*factor); END LOOP; END piped_func; / SELECT * FROM TABLE(piped_func(2)) WHERE rownum < 5 /

Anonymous    May 01, 2006
Printed
Page 65
in the sample code the two lines following the "BEGIN"

The example code had the following lines BEGIN PIPE ROW(dad_in); -- identify stream input PIPE ROW(mom_in); -- identify stream input This was completely wrong. The PIPE ROW function only pipes output and not input. If these two PIPE ROW lines are removed then and only this is the example correct. AUTHOR'S REPLY: The example NOW READS: CREATE OR REPLACE TYPE num_tab_typ AS TABLE OF NUMBER / CREATE OR REPLACE FUNCTION piped_func(factor IN NUMBER) RETURN num_tab_typ PIPELINED AS BEGIN FOR counter IN 1..1000 LOOP PIPE ROW(counter*factor); END LOOP; END piped_func; / SELECT * FROM TABLE(piped_func(2)) WHERE rownum < 5 /

Anonymous    May 01, 2006