Skip to main content

UKOUG 2009 recap

By

Last week I had the pleasure of visiting the UKOUG Technology & EBS Conference. The 3 days of presentations and social networking started already on Sunday evening with the ACE dinner - very well organized by Mark and Debra. Thai food combined with good company is proven to be an excellent combination!
Amongst all the tracks I picked the ones on APEX 4.0, Forms-to-APEX conversions and some DBA / CBO / SQL presentations.

APEX 4.0
One of the greatest (of many) interesting features of APEX 4.0 is - without any doubt - the Plug-In functionality. Anyone can define snippets of code that can be used in a declarative way in your application. By defining a Dynamic Action based on a Plug-In, you can probably do anything - only limited by your imagination! Plug-Ins are defined per application, but can be published and subscribed, like you can do with Templates. Oracle is planning to have a Plug-In repository at apex.oracle.com (or samplecode.oracle.com) containing the Plug-In code itself or a reference to it.
Other enhancements aiming at easier Ajax development are Page Level On-Demand Processes and simplified (and documented!) Ajax Javascript functions.
Some native Dynamic Actions will be native, like a GetData Plug-In: Think about a POST-QUERY trigger in Oracle Forms to retrieve and present data dependent on something you entered, like a location of a company.
More native item types will be added as well: Text with Autocomplete, Resizeable Text Areas, a new Rich Text Editor and the jQuery Datepicker.

The $60,000 question is of course: when will APEX 4.0 be available???
The APEX Development team aims at an hosted Early Adopter Release around New Years Eve. So that will be just after or even before....(all disclaimers apply). Of course the actual official release date is not revealed (they may not even know it themselves), but my bet is somewhere at the end of the first quarter of 2010.

Forms to APEX conversions
Apart from my own presentation (about Integration of Forms and APEX), there were a couple more handling this subject. Some of them handled the choice of the "best" development environment, while others brought up their experience with conversions of Forms to APEX. The most interesting was the one by the guys from Northgate who already converted 1,500 Forms to APEX and are in the middle of converting another 3,500 (!) Forms. They prove that APEX can really be an Enterprise Development Tool.

DBA / CBO / SQL presentations
As mentioned I also attended some non-APEX sessions, mostly lightweight DBA stuff. For the DBA diehards there were enough interesting ones to choose from - presented by the some of the most famous DBA gurus - , but I admit that a lot of them were probably way over my head.
The ones I attended (Tom Kyte, Jonathan Lewis, Piet de Visser) had all one thing in common: don't be afraid to overload your indexes with more than the minimal set of columns that you need to enforce data integrity and prevent unnecessary locking. You can achieve performance gain on query when you (sensible) add columns that you're using in where-clauses and order-by's. Of course maintaining these indexes (on insert and update) will increase overhead, but as long as you retrieve your data more often than you insert/update it, it might lead to an overall performance gain. You can even extend this idea to the limit, by creating an index containing all columns of your table (then you'll get an IOT - Index Organized Table). If the optimizer uses that index, your table won't even be touched as all data will be retrieved from the index.
But as always: test, test, test....

All in all it was another great conference. Thanks to all who put in the effort to come up with a presentation and all the others that made such great company!
Already looking forward to next year!

Comments

Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
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
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
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
Post a Comment
Read more

Stop using validations for checking constraints !

By
 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
Post a Comment
Read more