Skip to main content

Earplugged, Blindfolded and Jetlagged

After a long long journey I finally made it to my hotel next to San Francisco Airport. I can see the planes as they come and go, but luckily can't hear them.
The first leg of my trip, from Amsterdam to Cincinnatti, wasn't that bad: I had a complete row of three chairs for myself! Delta provided everyone with earplugs and blindfolds, so I stretched my legs and took some naps (still don't know if it is a good idea to take as much sleep as you can on a flight or to try to stay awake as long as you can, in order to survive a none hour time lap). The offerings on the entertainment system where good enough and even the food was ok.
I had less then two hours to change planes in Cincinnatti, and - with the experiences of the Sam Francisco and Houston Immigration lines - I wasn't certain that that would be enough. To my big suprise there was no line at all (I don't want to call three people in fron of me a 'line')! I even had to wait at the luggage belt before my suitcase arrived.
The second leg was worse. The airplane was completely booked, and there were lots of children aboard. I don't have anything against children (I have two of my own), but they don't make me happy when they're sitting right behind me and play around with the table tray and kick against the chair every time I almost fall asleep.
And also the service for this part was very minimal: no inflight entertainmant, only food for purchase and too few beverages. But what can you expect when you go for the cheapest option (only 450 euro ($600,-) for the complete trip).
In my hotel I stayed awake until 9:30 and then fell in a deep sleep. From which I woke up at... 3 AM! With some effort I managed to stay in bed, with some little naps, until 6. After breakfast I'll go to the car rental to get my car and drive the scenic route to ... Monterey!
Post a Comment

Popular posts from this blog

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…

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 …

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…