Skip to main content

The joy of international travel ... not

This morning I arrived rather early at SFO. When checking in I noticed that the first leg of my trip was delayed by almost 2 hours. And, originally, had a 1.5 hour layover in Minneapolis. So that wouldn't work anymore...
So Delta rescheduled my whole trip: From San Francisco to Los Angeles to Paris to Amsterdam. With a couple of hours of layover at each stop. Initially I would arrive around 11 AM in Amsterdam, but that will be around 8 PM now! So a nice 9 hour delay.
Luckily SFO offers a free 45 wifi service. As I have three wifi enabled devices I am fine for over 2 hours. I must get as much sleep as possible at every leg, to feel just a little bit alive tomorrow. Or the day after that. The one and only positive thing is that I can head straight to bed when I finally get home.
I really realty hope no other delays will pop up... (to be continued)

The continuation
So SFO - LAX took about 1,5 hours, then 3 hours of waiting. Next a 9 hours flight to Paris, and of course I got a seat right in the middle of the plane (no aisle, no window). Managed to get some sleep though. And saw a really nice movie: Greenberg. With Ben Stiller in a much less funnier role than usual. And the first part of When You're Strange, a "Rockumentary" about The Doors. Saved the second part for the next morning. Managed to get some sleep. Then in Paris another 4 hours of airport lallygagging. Another 1 hour flight to Amsterdam, a 1,5 train ride and then - finally - home. And also my luggage made it...
So a very, very, long trip indeed. But OOW was worthwhile. Again.
2 comments

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…