Skip to main content

Oracle APEX Cookbook [Second Edition] - Book Review

Recently the second edition of the APEX Cookbook has seen the light. As I haven’t read the first edition - I know, shame on me - I can’t exactly point out what the differences are, but that doesn’t really matter anyway. I guess no one will buy both versions anyway…

The book follows a different approach than most of the tech books I read (and wrote): Every issue is attacked with a recipe, existing of these steps:
1. Getting ready : Buy the groceries, get the pots and pans; or in APEX terms, do the necessary preparation like create a page or download a JavaScript file.
2. How to do it … : A step-by-step walk through to create the solution.
3. How it works … : A, usually short, explanation of the new or remarkable things you’ve just done when following the steps in the previous paragraph.

So if you don’t like this approach, you can skip te book - and the rest of the review as well. In my opinion, it might work when you’re looking to solve a specific problem - like including Google Maps in your application - but it doesn’t quite read as a novel. There’s no building up in complexity or an increase of tension in the book. It makes it somewhat “dry”…

But, as I said, if you’re looking for a step-by-step approaches of a lot of totally different problems: this is your book of choice! It’s written well, the steps are easy to follow and the code samples are all downloadable.
One thing that’s really stands out because it isn’t covered in a lot of books (if at all), is Websheets. There’s a complete chapter in this one covering all necessary information. There are also chapters on plugins and mobile, but of course these can’t compete with the whole books that are written on these subjects. But if you just want to get to first base, it’s excellent.

In general the book is aimed at beginner to intermediate developers. And even (more) experienced ones might find something useful, like a different approach to a problem, in this book.

So a four star rating f(out of five) rom my side !
Link to publisher's site
Link to Amazon
Post a Comment

Popular posts from this blog

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…