Earplugged, Blindfolded and Jetlagged

After a long long journey I finally made it to my hotel next to San Francisco Airport. I can see the planes as they come and go, but luckily can't hear them.
The first leg of my trip, from Amsterdam to Cincinnatti, wasn't that bad: I had a complete row of three chairs for myself! Delta provided everyone with earplugs and blindfolds, so I stretched my legs and took some naps (still don't know if it is a good idea to take as much sleep as you can on a flight or to try to stay awake as long as you can, in order to survive a none hour time lap). The offerings on the entertainment system where good enough and even the food was ok.
I had less then two hours to change planes in Cincinnatti, and - with the experiences of the Sam Francisco and Houston Immigration lines - I wasn't certain that that would be enough. To my big suprise there was no line at all (I don't want to call three people in fron of me a 'line')! I even had to wait at the luggage belt before my suitcase arrived.
The second leg was worse. The airplane was completely booked, and there were lots of children aboard. I don't have anything against children (I have two of my own), but they don't make me happy when they're sitting right behind me and play around with the table tray and kick against the chair every time I almost fall asleep.
And also the service for this part was very minimal: no inflight entertainmant, only food for purchase and too few beverages. But what can you expect when you go for the cheapest option (only 450 euro ($600,-) for the complete trip).
In my hotel I stayed awake until 9:30 and then fell in a deep sleep. From which I woke up at... 3 AM! With some effort I managed to stay in bed, with some little naps, until 6. After breakfast I'll go to the car rental to get my car and drive the scenic route to ... Monterey!

Comments

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

Roels Blog

Search This Blog