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

Fix Interactive Report headers issue when using a Region Display Selector

By
When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.
Post a Comment
Read more

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more