ODTUG Kaleidoscope 2008 : The day before

After an 18 hour trip from my home I arrived at the Sheraton in New Orleans. Luckily this time I also got my bag (at OOW 2007 it arrived a day later). A small wonder, because my transfer time in Houston was reduced from 1 ½ hour to 20 minutes due to the border control officer, who seemed to be very interested in all my predecessors in the queue. So I had to run from gate E to C. On the way I saw at a screen that The Netherlands where ahead against France with 1-0. At the time I arrived in New Orleans I called home and found out it turned out be a 4-1 victory!

When I came outside of the airport the tropical atmosphere hit me. It was about 32 C, but very very humid. After dropping of my luggage and freshening up a little in my room at the 43 floor, overlooking the Mississippi, I went out into the French Quarter. This area is packed with bars and restaurant and every bar seemed to have it’s own live music. I managed to stay awake until 9pm - that makes about 22 hours awake - and slept until 6:30 the next morning.

When I stepped out for a nice and quiet stroll through the French Quarter and the riverside it was so hot and humid already - or still - that my sunglasses blurred immediately. Like stepping into a tropical swimming pool. After my walk I took the old steamboat for a trip over the Mississippi and strolled over the Cajun / Zydeco and Tomato festival. New Orleans is very very lively: there is music on every corner and food stalls in between them. And of course the obvious street artists painting, breakdancing and reading hands. In this part of town there is not much damage left from Katrina three years ago, but also it didn’t suffer that much from The Storm as the locals seem to call it.

I hope I am over my jetlag already and ready for the start of the conference tomorrow morning at 8:30 : a full day ‘APEX Must hear success stories’

For those who are more of the visual type, I uploaded some pictures here.

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

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