Skip to main content

UKOUG Day 3

The (rather ambitious) schedule for today was :

Lost in JDeveloper by Sten Vesterli : Sten guided the (Forms experienced) audience in creating an ADF Swing Client App ofcourse declaratively (next to AJAX this is the buzzword of the conference : everything should be declarative, you can be a programmer when you' re able in controlling your mouse ;-) ).
'Christmas
Programming Real Applications with APEX by Andrew Woodward : Again everything declarative but now using APEX instead of JDev. The point was: you can create simple applications faster than using Oracle Forms but when you need more advanced features you'll need to program Javascript and AJAX. But that's only temporarily, because in the next version(s) you also will be able to create AJAX components declaratively.

Modelling on the cheap by Andrew Clarke (I chaired this one) : Andrew sketched out the pros and cons of different modelling tools - from whiteboards to (free) datamodelling tools. As far as he knows the best free datamodelling tool on the market today is Schemester.

Oracle SQL Developer Advanced Features by Sue Harper : Sue pointed out how to make our own extensions - as extra tabs and right-mouse-options - on SQL Dev and demonstrated the power of the Migration Workbench. Also APEX content in your database is visible throug SQL Dev and a nice new feature (in the next version) will be to possibility to view trace files as a very flexible TKProf like output!

Oracle Forms Roundtable by Grant Ronald : In this round table all attendees could present their views on Oracle Forms and what features should be added in subsequent releases. Alas not much came out - I think we are so "comfortable" with the imperfections of Form... Grant suggested a couple of enhancements like a kind of JTable option (where you can click on the header for automated sorting etc) and a new look-and-feel / color scheme. Ofcourse no fixed promises where made...

Integration of BI Publisher and APEX by Dimitri Gielis : Dimitri, enthousiastic as ever, showed the possibilities of using BI Publisher for creating very good looking reports. The integration between the two products is very good. But a great disadvantage is that BI Publisher is not as free-of-charge as APEX is (maybe this is Oracle's way to earn some money out of APEX - apart from the database licenses?).

Special : Trevor Baylis - a World Famous British Inventor : Trevor, a 72 years old 'world famous' inventor (I never heard about him, but he is the inventor of, amongst a lot of other stuff, the wind-up radio - now I understand why we've got one from the organisation) presented his views on " invention". In his opinion you can learn to invent and, just like there is a School of Arts, there also should be a School of Inventions. The presentation was very amusing.

Event Dinner : One hall was transformed into a ' Christmas Eve' kind of room and we all enjoyed the drinks, food and (more or less) the DJ...

Comments

Popular posts from this blog

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

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

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