Skip to main content

Travelling to OOW 2010

Yesterday was one of those days. Crossing the Atlantic and ending up with crossing 9 timezones. So that day had 33 hours...(so you can definitely have more than 24 hours in a day!).
I got up at 6 AM, traveled to Schiphol (Amsterdam Airport) by train. At Schiphol it was crowded! People with large bags everywhere, no one standing in line. Giant congestion for the border security etc. And then there is the obligatory chat with a security officer when boarding (did you pack your bag yourself, brought anything etc..). The strange thing is the US carriers seem to be obliged doing that - but only for inbound flights??
But the good thing was: I managed to upgrade my first leg of the trip (to Minneapolis). Never traveled Business Class before, but, man! what a joy!. Imagine long, broad seats with lots of buttons on the armrest. If you use the right ones, you can get the chair in a 100% horizontal position - while massaging your back! And then there is the drinks and the food... I would love to travel this way every time, but hey, budget is limited - and frequent flyer miles are too.
In Minneapolis I had originally a 1,5 hour layover, but when we arrived it was shrunk to 1 hour. With one airplane full of Japanese visitors in front of my at the border security. Luckily it took only around half an hour to pass the security, so a good half an hour left to grab a coffee and walk to the connecting plane. No business class this time, but a crowded economy. So: Plug in iPod and close eyes...
Got a cab in SF to the house (Jacco rented it - with his girlfriend Margot), got some good food with the three of us, had a few beers and went to bed around 10 PM. 
And of course woke up at 2.30, 3, 3.30, 4.15, 5.45...and finally got out of bed and made myself a coffee. 
Looking forward to the rest of the day: Usergroup sessions, Keynote, ACE Dinner...here I come!


1 comment

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 …