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!


Comments

Doug Burns said…
OOW and the best of company? Now you're just rubbing it in!

Have a good one and say hi to Jacco and Margot from me.

Cheers

P.S. At least Jacco can have a relaxing time this year and won't have to worry about being my counsellor/bodyguard ;-)

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function