Oracle Web Applications
by Andrew Odewahn


This errata page lists errors corrected in the 3/00 reprint.


Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification



{122} 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."



{149} In table 7-12, the decription for version 4 did read:

	"Procedural version of version 4."

It now reads:

        "Procedural version of version 3."



{196} In the second sentence, it did read:

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

It now reads:

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



{199} 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.


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



{212}  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.