Skip to main content

UKOUG 2010 Recap - Wednesday

Wednesday I started late, because I skipped the first session to prepare for my second one "Tales from a Parallel Universe: Using 11gR2’s Edition Based Redefinitions". Went also pretty good as well I think, ended nice on time - even, again, with a session chair. And I received some really positive feedback from people like John King and Christian Antognini. Thanks guys!
Then there was a funny debate kind of session between Tony Hasler and Jonathan Lewis about "Does Oracle ignore hints?". In the end it was all about semantics...if you discard bugs, poor or wrong documentation and more or less hidden features and unexpected optimizer processes, Oracle never ignores your hint (which in fact is more a 'directive' than a hint) - otherwise you might say that Oracle actually does  ignore your hint.
After lunch - instead of the good hot lunches we received a school-like lunch bag this time - I chaired my second session : "Edition-Based Redefinition: Testing Live Application Upgrades (Without Actually Being Live)". Because I already was familiar with the subject at hand, there wasn't very much new stuff in there - but I am always curious to see if I missed someting in my own presentation...
The last session of the event I attended was "Still using ratios" by my colleague Piet de Visser. Due to the worst time slot of the week - and the weather -  there were only a few attendees (around 10). The content was good though. He should have the chance to redo that presentation on a better time!
Then the people that didn't left Birmingham (or couldn't) all winded down in All Bar One and O'Neills for some final drinks and talks.
All in all again a good conference qua content and attendees. Always good to catch up with people you only met a couple of times a year during this kind of events. Hope everybody made it back home eventually and already looking forward to the 2011 edition of the conference!

Comments

Jon Barwell said…
Enjoyed both your presentations. Your presentation on Edition based Redefinitions was really interesting even though it convinced me it was something I don't need to know at the moment.

Popular posts from this blog

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

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

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