Errata

Oracle Web Applications: PL/SQL Developer's Intro

Errata for Oracle Web Applications: PL/SQL Developer's Intro

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 xi

(xi) The name "Dave Kreikel" in the acknowledgments now reads "Dave Kreines."

 Anonymous    Dec 01, 1999
Printed
Page 38,186
PL/SQL listing of show_emps

In the PL/SQL listing of show_emps on page 38, it reads

PROCEDURE show_emps (
i_job .......
)
AS

Can also read as:

PROCEDURE show_emps (
i_job ........
)
IS

Either syntax is correct.


 Anonymous   
Printed
Page 113
Last sentence of the second to last paragraph

The last sentence of the second to last paragraph now reads: "...if the datatype is NUMBER(4,1); it would be 1500 if the datatype is
NUMBER(4,-2)."

Should read:

"...if the datatype is NUMBER(5,1); it would be 1500 if the datatype
is NUMBER(5,-2)."


 Anonymous   
Printed
Page 122
Second to the last sentence

The second to the last sentence on the page did read

"These elements can be any simple scalar datatype, like
a number, date, or string; unfortunately, you can't use
complex types like records or other index tables."

It now reads:

"These elements can be declared as simple scalar datatypes,
such as strings, or as more complex types (in Oracle 7.3 and
above), such as records. However, you can only pass scalar
types from the Web."

 Anonymous    Mar 01, 2000
Printed
Page 149
Table 7-12

In table 7-12, the decription for version 4 did read

"Procedural version of version 4."

It now reads:

"Procedural version of version 3."

 Anonymous    Mar 01, 2000
Printed
Page 149
line 8

The following line has been inserted in line 8 (between the IS and BEGIN):

line_copy VARCHAR2 (32767) := line;

 Anonymous    May 01, 2000
Printed
Page 150
Code entry

In the code entry at the top of the page,the third line from the bottom (OWA_PATTERN.change..) has been changed to the
following:

owa_pattern.change ( line_copy, from_str, to_str, flags);

3. In the code entry at the top of the page, change the next to last line did
read: "HTP.PRINT('</td></tr></html>');".

Now reads:

"HTP.print('</td></tr></table></html>');"

 Anonymous    May 01, 2000
Printed
Page 190
12th-19th lines of code

The 12th-19th lines of code on the page now read

LOOP
INSERT INTO responses (response_id, question_id, answer_id)
VALUES (
response_seq.nextval,
question (item_count),
response (item_count)
);
END LOOP;

Should read:

LOOP
INSERT INTO responses (response_id, question_id, answer_id)
VALUES (
response_seq.nextval,
question (count),
response(count)
);
END LOOP;

 Anonymous   
Printed
Page 196
Second sentence

In the second sentence, it did read

". . . MEMBERS is defined recursively . . ."

It now reads:

". . . MESSAGES is defined recursively . . ."

 Anonymous    Mar 01, 2000
Printed
Page 199
Third line from bottom in the code section

The third line from bottom in the code section did read

HTP.print('</table>');

This line of code has been deleted from the print_terxtarea_row procedure.

 Anonymous    Mar 01, 2000
Printed
Page 201
List of the PROCEDURE login_forum

List of the PROCEDURE login_forum, the statement HTP.print('<table>') has been added just before the first general_form.print_input_row statement.

Anonymous    Mar 01, 2000
Printed
Page 212
The section of code starting with "PROCEDURE save_message"

The section of code starting with "PROCEDURE save_message," has been modified:

In the section of code starting with "INSERT INTO messages (", a
comma has been added after "msg_body", and "date_created" inserted
as the entry in a new row just below this.

In the section of code starting with "VALUES (", a comma has been
added after i_msg_body" and "SYSDATE" has been inserted as the entry
in a new row just below this.

 Anonymous    Mar 01, 2000