Skip to main content

ODTUG Kaleidoscope 2008 : Day 4 - ADF vs APEX and Wrap Up

Image
By
The last morning of this years ODTUG was completely filled with one three hour session: APEX versus ADF 'shootout'. Although the presenters, Lucas and Dimitri, quickly stated that there was no violence to be expected, the audience was hoping for some clear statements.

Lucas and Dimitri both built an application using their favorite tool and demo'ed it to the audience. Both failed on one part - as live demo's tend to do - so it was 1-1 at mid time. After the break the match continued with some nice features shown on both sides. Both presenters where dared to say something positive on the other tools. For Dimitri this was the most difficult part: "I can't come up with anything nice to say about JDeveloper".

After a complete comparison, there was one clear winner: The audience!

Thanks to both of you guys for this joint effort!

So to wrap up: ODTUG is a great event. Not great in the sense that you're overwhelmed with 1,000's of people (there were about 700 attendees), but exactly the opposite. Due to the fact that it is rather small, you'll find yourself having a beer (or two) with all kind of guru's, experts, co-bloggers etc. Especially that relaxed, cool atmosphere is what makes ODTUG such an excellent event.

One more note about 'atmosphere': New Orleans in June is so hot and humid, that you barely can stand the outside temperature for more than 10 minutes - on the opposite : inside (in particular inside the Sheraton) the air conditioning is turned to the max. So every time you get from the outside to the inside, or the other way round, you have to deal with a temperature difference that feels like a 20 C.

Also the Sheraton is a good place to stay and from the 43th floor I had a great view on the river. Could have been better if somebody had cleaned the window - but who cleans windows at that height?

I hope to see everybody again next year - in Monterey (?).
Labels:

Comments

Anonymous said…
> For Dimitri this was the most difficult part:
> "I can't come up with anything nice to say about JDeveloper".

LOL!!!

Darn, and I thought this was going to be a balanced comparison! :-)
3:11 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 o...
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