|
Oracle SQL and PL/SQL Handbook: A Guide for Data Administrators, Developers, and Business Analysts
 |
Author: John Adolph Palinski
List Price: $39.99
Our Price: Click to see the latest and low price
ISBN: 0201752948
Publisher: Addison-Wesley Pub Co (08 August, 2002)
Edition: Paperback
Sales Rank: 213,478
Average Customer Rating: 3.6 out of 5
|
Customer ReviewsRating: 1 out of 5
Many errors in text
Palinski is full of errors, confusing and sometimes contradictory explanations. It seems to have been written by someone who is unfamiliar with Oracle, and just blindly compiled material from different sources.I had to check every topic by referring to other documents and manuals. In the beginning, you see this book is like college text, not for working Oracle person. I have more than 15 years experience in Oracle and did not find it useful.
Rating: 5 out of 5
Author of the book - realistic@radiks.net
The review by the reviewer from Lincoln does not pertain to this book. The book pertains to my book "Oracle Database Construction Kit" that was written in 1997 and is out of date even though the publisher continues to market it. At the time "Oracle Database" was published Forms Builder 4.5 was the current product and Oracle8 was just released. Oracle8i was still several years away. Please disregard his comments concerning this book since they do not pertain. In fact, this book does not even cover the Oracle development tools.
Rating: 2 out of 5
OK, but lacking
There are only four pages on Oracle 8i. This book is written for the outdated Forms Designer 4.5. What a disappointment! The newer Oracle Forms Builder 6 is considerably different. Furthermore, the forms used in the exercises often will not compile, (because the author made the unfortunate choice of the PL/SQL-Forms reserved word "TOOLS" for one of the table names). You can drop the TOOLS table and create it with another name to make the examples work.
Some example forms need additional debugging. Taking empch14x.fmb as an example, this is what you need to do:
1. Set mapping of other values to ?M? for the Gender item in data block one.
2. Change the post query trigger to point to the correct file location for the images. For example: filename := 'c:\palinski\ch14\'||to_char(:one.payroll_number)||'emp.tif';
3. Also in the post query trigger, you may need to change the ?filename varchar2(25);? to something longer such as filename varchar2(30); to handle a longer path name.4. Open the property palette for block two and change the Query Data Source Name and DML Data Target Name to the name of the re-named tools table. For example, if you renamed the TOOLS table to P_TOOLS, then enter the name P_TOOLS here.
Once these changes are made, the form works well and displays a TIF image associated with each record.
5. Open the property palette for the relation between block one and block two. Change the name of the TOOLS table to the name of the re-named tools table. Another example is form DirCh16.fmb. This is a ?directory? form, useful for finding records in large tables. To make this form work, open the property palette for block one and set Database Data Block = ?No?. This example form should have used parameters in the call to the next form, but instead the author used an unusual home-baked solution to pass a parameter to the called form.
The text omits instructions on how to pass parameters to a form using a parameter list, and instead describes a makeshift way of adding a non-database block to a form to pass a variable. Students would be better off to use a parameter list as Oracle intended.
Chapter 17 on reports briefly covers outdated Reports 2.5, which helps little towards learning Oracle 8i?s Reports 6. Chapter 18 explains how to customize and create reports manually.
Similar Products
· TOAD Pocket Reference for Oracle
· Learning SQL: A Step-By-Step Guide Using Oracle
· Fundamentals of Database Systems, Fourth Edition
· Essential Oracle8i Data Warehousing: Designing, Building, and Managing Oracle Data Warehouses
· Practical Web Database Design
|
