Skip to main content

UKOUG Day 2

After yesterdays Blogger Meetup it was hard to start the day...
The first session of the day was Sue Harper's talk on SQL Developer Latest Features. She mainly focussed on the new / enhanced features of version 1.5, that will be production somewhere (early?) 2008. To name some new features : external authentication (OPS$ users), browsing queues and Java, schema differences and schema copy, recall filters and a flashback query tab, formatter enhancements, your own code templates and drill down reports. With very new version SQL Developer looks more like the current TOAD version ;-).

After that I visited a session about Building Rich UI with APEX and AJAX. It was pretty impressive what you can do with a combination of APEX and AJAX (look at ajaxpatterns.org. The presenter also showed the use of widgets of the jQuery UI library like an accordion and a fancy date picker (jquery.com).

The next session about the Roadmap for legacy system migration I chaired. A solution for the upgrade to Designer / Developer 10g was presented that can' t compete with our Famous solution! The most interesting part of this presentation was the use of Dataload Classic (dataload.net) for playback testing (recording actions in the old forms, playing it back in the new ones).

After that one I went to see Grant Ronald on AJAX UI Development with JSF and ADF Faces. The good news is that we don't have to worry about the (complicated) AJAX stuff, because it's all hidden after the new ADF Faces Rich Client UI objects. And they look really great : Accordions, drag and drop etc.

Next on the program was a session on Rules Manager and Expression Filter: a way to let Oracle watch for incoming data conforming a specific where clause. You can use this feature for information distribution or workflow. Sadly to say that it needs a lot of difficult steps to set up.

Last but not least was Steven Davelaar (again chaired by me) enthousiastic as ever telling en demoing JHeadstart. He showed the new (version 10.1.3) features on Security, Dynamic Menu's, Multi Language Support and Flexible Items. The most impressive news is that also for JHeadstart Oracle is working on a Release 11 version - with all the beautiful AJAX features.... As allways it was hard to keep him to the time schedule ;-).

And now off to the ' community focus pubs' .

Comments

Popular posts from this blog

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

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