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.
| Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
| PDF |
Page 111
Figure 4-5. |
The query for the outer join is:
SELECT p.project_name, ph. employee_id,
ph.time_log_date, ph.hours_logged
FROM project p JOIN project_hours ph
ON p.project_id = ph.project_id;
That's seems a inner join to me (same as above in book)
Should be:
SELECT p.project_name, ph.time_log_date, ph.hours_logged
FROM project p LEFT OUTER JOIN project_hours ph
ON p.project_id = ph.project_id;
Note from the Author or Editor:
I can't find a copy of my book to see the error in context, but I believe you to be correct. If I called the join an outer join, then I should have written the words LEFT OUTER. |
Christian Floreck |
Jan 28, 2014 |
|
| Printed |
Page xix
The text of the "How to Contact Us" section has been updated. It now |
reads:
How to Contact Us
The information in this book has been tested and verified, but you may find
that features have changed (or you may even find mistakes!). You can send any
errors you find, as well as suggestions for future editions, to:
O'Reilly & Associates, Inc.
101 Morris Street
Sebastopol, CA 95472
(800) 998-9938 (in the United States or Canada)
(707) 829-0515 (international/local)
(707) 829-0104 (fax)
There is a web page for this book, where we list any errata, examples, and
additional information. You can access this page at:
http://www.oreilly.com/catalog/9781565925786/
To ask technical questions or comment on the book, send email to:
bookquestions@oreilly.com
For more information about our books, conferences, software, Resource Centers,
and the O'Reilly Network, see our web site at:
http://www.oreilly.com
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page xix
The following information was added the preface |
"How to Contact Us
We have tested and verified the information in this book to
the best of our ability, but you may find that features have
changed (or even that we have made mistakes!). Please let us
know about any errors you find, as well as your suggestions
for future editions, by writing to:
O'Reilly & Associates, Inc.
101 Morris Street
Sebastopol, CA 95472
1-800-998-9938 (in the U.S. or Canada)
1-707-829-0515 (international/local)
1-707-829-0104 (FAX)
You can also send us messages electronically. To be put on
the mailing list or request a catalog, send email to:
info@oreilly.com
To ask technical questions or comment on the book, send
email to:
bookquestions@oreilly.com
We have a web site for the book, where we'll list examples,
errata, and any plans for future editions. You can access
this page at:
http://www.oreilly.com/catalog/9781565925786/
For more information about this book and others, see the
O'Reilly web site:
http://www.oreilly.com"
|
Anonymous |
|
Feb 01, 2000 |
| Printed |
Page 25
|
The listvariable description for "scriptfile" did read:
"Is the name of a SQL*Plus script file you want to run.
SQL*Plus will start up, execute the file, and then exit."
Now reads:
"Is the name of a SQL*Plus script file that you want to run.
Be sure to end your script with an EXIT command."
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 25
The last italicized heading near the bottom of the page did read: |
"arg1 agr2 arg3"
Now reads:
"arg1 arg2 arg3"
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 51
|
The first text paragraph on the page read:
Notice that line 4 has been replaced by the text that was
typed after the numeral 4 on the first line of this example.
Notice, too, that the leading spaces used to indent AND were
lost. That's because when you type a new line of text as an
argument to a command, SQL*Plus takes the first non-blank
character as the start of that line. That's usually not much
of an issue. If you are line editing, you are just trying to
get the command to run.
It now reads as follows:
Notice that line 4 has been replaced by
the text that was typed after the numeral
4 on the first line of this example. You can
replace any line in this way. If you want to preserve
the indenting, you can insert extra spaces following
the line number.
|
Anonymous |
|
Sep 01, 1999 |
| Printed |
Page 57
In chapter 2 (page 57), I told you that you could customize |
the SQL*Plus editor, and referred you to chapter 11 for more
information. Unfortunately, I didn't put that information in chapter
11. I apologize for that oversight.
SQL*Plus uses the user variable named _EDITOR to point to the
executable to be invoked in response to the EDIT command. Under
Windows 3.1/95/NT/98/2000/whatever, the default setting is "NOTEPAD".
You can change this value to point to any editor you like. The
following example sets the editor to WordPad
define _editor="C:PROGRA~1ACCESS~1WORDPAD.EXE"
The DEFINE command only changes the setting for the current session.
To make the setting permanent, place the DEFINE command in your
login.sql file. That way it will be executed each time you start
SQL*Plus. Chapter 11 in the book contains more information about
login.sql
The last sentence currently used to read:
"Chapter 11 tells you how to do this."
Now reads:
"Do this by defining the user variable named _EDITOR to
point to executable of the editor you want to use."
|
Anonymous |
|
Feb 01, 2000 |
| Printed |
Page 84
Deleted the COMMIT statement in the code example in the middle of the |
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 85
Deleted the COMMIT statement towards the end of the large code example. |
(Chapter 4) All the notes and warnings in this chapter were missing their
icons. Here is a list of the icons that were inserted on the relevant pages:
p. 123 - owl
p. 134 - owl
p. 140 - owl
p. 141 - both owls
p. 148 - owl
p. 150 - turkey
p. 153 - owl
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 150
|
The first sentence in the first paragraph did read:
"There are only two ways to deal with this problem."
Now reads:
"There are at least two ways to deal with this problem."
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 150
The first paragraph did reads: "Their are only two ways..." |
Now reads:
"There are only two ways..."
|
Anonymous |
|
Jun 01, 2000 |
| Printed |
Page 183
In the left column of Table 6-2, near the bottom of the page, |
it read:
NUM_ROW
Now reads:
NUM_ROWS
|
Anonymous |
|
Feb 01, 2000 |
| Printed |
Page 186
In Table 6-4, "U = UNIQUE KEY" has been added to the contents |
column for the CONSTRAINT_TYPE field.
|
Anonymous |
|
Feb 01, 2000 |
| Printed |
Page 196
In the second line of the comment in the code sample, changed "seperate" |
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 200
In the book, I state that you can get the definition of a check |
constraint just by looking at the ALL_CONSTRAINTS table. Indeed you can. The
definition is in the SEARCH_CONDITION column. However, what I said in the book
may leave the impression that the ALL_CONS_COLUMNS view is irrelevant for
check constraints.
That's not true. The ALL_CONS_COLUMNS view is still relevant. With a check
constraint, ALL_CONS_COLUMNS can be used to identify the columns involved. It
won't get you to the exact formula used for the check condition, but it will
tell you which columns are used in that formula.
Thanks to Ron Joffe for bringing this very subtle issue to light.
|
Anonymous |
|
|
| Printed |
Page 216
In the first sentence under "Running the SHOW_TRIGGER.SQL script," |
changed "TEST_1" to "EMP_HIRE_DATE_CHECK".
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 239
In the 11th line of the 2nd code sample, changed "prompt" tp "PROMPT". |
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 348
In the code line "ARCHIVE LOG START [TO destination]" the closing |
bracket is now in regular cw, not cw italic.
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 382
The first sentence in the fifth paragraph on the page, under the "SET |
TRIMSPOOL" heading, did read:
"...you will want to leave TRIMSPOOL ON."
Now reads:
"... you will want to leave the TRIMSPOOL OFF."
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 424
The last italicized heading near the bottom of the page did read: |
"arg1 agr2 arg3"
Now reads:
"arg1 arg2 arg3"
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 448
Changed "delete" to "list" in the referenced text. |
|
Anonymous |
|
Sep 01, 1999 |
| Printed |
Page 482
About 2/3 down right-hand column, changed the entry "commenting scrips" |
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 482
About 2/3 down right-hand column, the entry "COMMIT statement, |
disabling feedback from" now includes page 84.
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 503
In the 3rd paragraph under "About the Author," changed "Lansing, |
Michigan" to "Munising, Michigan."
|
Anonymous |
|
Dec 01, 2000 |
| Printed |
Page 504
The following RepKover information was added to the Colophon |
Whenever possible, our books use RepKover(TM), a durable and
flexible lay-flat binding. If the page count exceeds RepKover's
limit, perfect binding is used."
|
Anonymous |
|
Feb 01, 2000 |