Skip to main content

OOW2008 Afterthoughts

Image
By

As Oracle Open World 2008 is 1,5 week behind us, it is about time to finish up my posts on this subject - and get rid of my notes. So let's take a quick look on the sessions I didn't mention already.


Forms2APEX Migration
David Peake introduced the "soon-to-come" APEX 3.2 release. The most important new feature (or maybe the only new feature) is the support for migrating Oracle Forms to APEX. He emphasized that there is no need from an Oracle support perspective to move from Forms to APEX. You should only go for this route if there is a sufficient business justification for it. A migration from Forms to APEX has to be considered as a real project, consisting of Analysis, Design, Convert, Post Migration, Acceptance and Training. The Forms2APEX toolkit is in no way a silver bullet. There will be a lot of handcraft involved to achieve acceptable results. Especially for more complex Forms you'll need a lot of effort to get similar functionality in APEX. Luckily the tool helps you to identify non converted code. Coming to a theatre near you at the end of 2009....

Inside the Oracle 11g Optimizer: Removing the mystery
A session somewhat out of the APEX scope, but nevertheless very interesting. The highlights of the new 11g optimizer stuff are:
  1. Full control over the execution plans, using SQL Plan Management (SPM). Using SPM, a change in an execution plan has to verified before it is actually used.
  2. Extended Optimizer Statistics to collect statistics over a group of columns.
  3. Improved Statistics Collection :
    1. AUTO_SAMPLE_SIZE - With the speed of 'estimate' (or even faster) you can get the quality of 'compute'.
    2. Incremental Global Statics for partitioned tables: global statistics are built from the partition statistics.
  4. Adaptive Cursor Sharing & Enhanced Bind Peeking: In version 10g and before an execution plan was determined by the initial value of a bind variable and the same execution plan is shared regardless the subsequent bind variables. But a select on emp 'where job=VP' returns only one row and will probably benefit of using an index on job. But if a select on emp 'where job=WORKER' returns 90% of the rows, the same execution plan is used. Starting from 11gR1 the same query can have more execution plans depending on the values of the bind variables. With Adaptive Cursor Sharing plans are shared when bind values are (more or less) the same and a new plan is generated when the binds are not equivalent.
Tom Kyte's Sessions
Tom Kyte did a number of sessions that week and I visited two. In one of the sessions - the Oracle Develop keynote - Tom did a great ad for APEX. He called APEX the best Oracle tool around, next to SQL Developer and SQL Plus!
Tom told the audience about his experience on the questions raised on the asktom-site. He gets a lot of questions regarding the tuning of queries. Most of the time the response is "Why would you do that?". So often it is better not to tune the query, but tune the question (or the process)!
In his session about managing change Tom announced that the long awaited Online Application Upgrade will be part of 11gR2 (ofcourse with the regular disclaimers). Oracle showed this impressive feature already at OOW in 2006 (see my post about that here), and it will finally make it into the next release of 11g!

The power of the APEX Repository
Patrick Wolf did an impressive presentation - with beautiful pictures ànd sound - on the repository. You can use the repository not only to store the APEX-metadata, but you can use the data inside also for quality checks, documentation, sitemaps, application page flow, generic code, monitoring and modification - using an export file or (more dangerous) directly in the tables.

Building large commercial applications with APEX
The guys from PAETEC impressed the audience with their presentation on the APEX version of Pinnacle, their tool for Service Life Cycle Management. It is a large application consisting of around 800 tables and 2000 pages in 19 applications. They build it in 2 years with 20 developers. So who dares to say APEX is only for Excel or Access replacement?
They extensively use the APEX repository to generate information on the pages and did some advanced tweaking by modifying the arrays used for rendering, just before the page is painted. Using their own framework they emphasized the separation of layers: Presentation with no validation at all, business rules using views and triggers and the data. So a three tier model, but with all tiers in the database!

Building a Web 2.0 interface with APEX
Marc Lancaster had the questionable honour to do the last APEX presentation of this OOW. He explained the advantages of Javascript, AJAX, JSON and external libraries. He is using ExtJS extensively on his demo site. To summarize:
• Takeaways
– AJAX doesn't have to use XML, or be asynchronous
– Javascript performance is rapidly improving
– Consider Namespacing when integrating Javascript libraries.
• Key concepts
– Start learning and using AJAX and JSON
– Progressively add functionality through templates
– Look for low hanging fruit
– Javascript libraries can do the heavy lifting
– Apex will us jQuery in version 4.0.
• Lessons learned
– Factor in time to build templates
– Always consider page loading performance.



Wrap up
To conclude, this year's OOW was again a huge event, and with lots of opportunities to attend good sessions, meet old friends and create new friends. Thanks to all who made this a unforgettable week!
Labels:

Comments

Monty Latiolais said…
Great post for those of us watching from afar.

Is the word that ApEx 3.2 isn't to arrive until late 2009?? I thought that was the timetable for 4.0 and that 3.2 was....soon. (I know that's a relative term)

Monty
7:58 pm
Roel said…
@Monty
To my knowledge (apart from all the usual Oracle disclaimers) APEX 3.2 will go beta "soon" - probably on apex.oracle.com - and 4.0 is planned "early" 2009....
Let's wait...
9:47 am
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