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.

Comments

Johan Bolhuis said…
Hoi Roel,

Een beetje troost voor je, morgen mag je de hele dag rusten. Alexandra en ik zitten op de bank snot verkouden te wezen, dus de afspraak is verzet.

Groetjes en een voorspoedige reis verder,

Johan Bolhuis

(Tip voor jou en Linda: www.lettinggo.tv kun je de movie als stream bestellen. Wij vinden het een aanrader.
saban_arslan21 said…
This comment has been removed by a blog administrator.

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

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 wors...

APEX ReadOnly Pages - The easy way

If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...