Bill Pribyl

An easy going, but quietly authoritative introduction to PL/SQL.

Why did I choose to read a book on a programming language if I am a software tester? One simple reaon:- I use it, every day in my work. The application I test, is built with it. I test at both System Test and Unit Test level. I am responsible for is both Unit and System testing. Although I might not actually design or execute the Unit Testing, I have to make sure it is accurate.

Thus to a certain extent I have to know what is happening underneath the bonnet.

What did I hope to get from the book. Firstly to Underpin my day to day experience. Secondly gain greater understanding of the PL/SQL language and architectures. Thirly be able to read PL/SQL code code (not write or read it fluently, just enough to see what is going on.). Finally ask less beginner type questions of the developers.

The concept of grey testing, is one which I find intriguing. Elfried Dustin's book Effective Software Testing: explores the idea that testing can never b truly Black Box or White Box. There comes a point, as a system tester, where you have to look at the code, or understand how a particular component functions. Conversely Unit testers have to an awareness of how their component fits into the wider world.

To help in my "grey box testing" I decided to read this book.

At which level is it pitched though? Quite clearly the book is targetted at complete novices to PL/SQL. The book does however need some prior knowledge of SQL and databases. For a more in depth book, the Otherwise look at Oracle PL/SQL Programming. The book is one of an O'reilly series, called simply "Oracle"

The style of book is to handhold the user, without being condescending to novices. Pace of the books is fast though!. As you would expect the early chapters are with the easy stuff. Smoothly, the complexity of the material increases as the chapterspass. Generally the author follows the same same example. Set in a library system it is satisfactory. Luckily it does not involve the author's cousin Jim Bob in some ludicrous storyline.

The pace of the book can be demonstrated with how the author whips through a discussion what PL/SQL is.

In a few pages, the reader is given an overview of the different kinds of programmining languages, SQL, how SQL has been "extended" to build PL/SQL, lastly what the procedural element is.

The bottom line is, Oracle users can use PL/SQL to program procedurally. Thus the programmer can define an ordered series of steps to produce a result.

"PL/SQL is a procedural (Algol-like) language with support for named program units and packages; much of its syntax is borrowed from Ada, and from Oracle's SQL it derives its datatype space and many built-in functions.

Accurate? As far as I can tell yes. Everything I learned, I have been able to discuss with a developer. Very scientific, I know. My use of improved PL/SQL searches has proved very successul. /p>

Does it succeed? On my criteria it does. My understanding of the product I test is much greater. In terms of reading code and talking to developers my knowledge has increased dramatically.

The only negative comments would be the chapters and material devoted to the web, using PL/SQL Server Pages (psp). As hardly anyone uses them in comparison to .JSP, ASP, or ASP.NET, you can comfortably skip them. Unfortunately the book does not come with a CD.

My personal recommendation would be 8/10. A good example, high retention of info and packed with tips on getting started. This book isa good read for everyone who is starting off from scratch or wants more.