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

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

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…