Skip to main content

Travelling is not always fun!

At Orlando airport my original flight via Detroit was delayed by three hours, due to "technical issues". So they rebooked me via Minneapolis. But that one was delayed too, due to "weather circumstances". But as that would affect all planes, the advice was to keep that route. And indeed the initial delay of 1,5 hours (I had a layover of 1,5 hours...), was reduced to 45 minutes when departing. But when the plane rolled back from the gate, the right engine didn't started. They had to replace the fuel filter. So it went back at the gate, they did the replacement and a half hour or so later we where again ready to depart. So rolled back again, but at that moment all electricity went down, because the third engine (used for electricity when the other engines aren't running) went down. Do they had to reboot the plane or something like that (did you know the in flight entertainment system runs on Linux?). So, again 30 minutes later we departed. At that time I had a scheduled layover in Minneapolis of -30 minutes. During the flight we could check the flight statuses, using the on board wifi, and the plane to Amsterdam was scheduled with a ... 30 minutes delay! Arriving in Minneapolis we had to wait for 10 minutes for a free gate. I got out of the plane as one of the first passengers, and ran all the way from gate G18 to G4 - which is a pretty nice exercise, even with the help of the moving sidewalk. Arrived at the gate on the exact (re)scheduled departure time. I got in the plane as last. They literally closed the door right behind me.
But then the plane had to be de-iced (hard to imagine when you're coming from Orlando!). But there seemed to be only one de-icing thing available at that time, 11:30PM, so we had to wait for nearly an hour...
Fell asleep very quick and stayed that way all across the Atlantic. Landed in Amsterdam just 2,5 hours later than my original schedule. So that was not too bad.
So now I am back in The Netherlands...but where is my bag???


- Posted using BlogPress from my iPad

Location:Train

5 comments

Popular posts from this blog

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…

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 …