Skip to main content

UKOUG 2010 Recap - Tuesday

Tuesday started of with a two hour Masterclass by Cary Millsap "Thinking clearly about performance". A really great session that explained clearly what performance actually is (so the content covered the title). Using with a lot of nice stories, examples and analogies Cary has the ability to explain stuff that seems difficult in a way everybody can understand. If you haven't seen this one, it is really a must see if you have the chance!
Because the next session on my agenda was shifted to another place and time a had some time to walk through my own presentation for that afternoon before attending the APEX Roundtable. A nice Q&A about what all APEX stuff. Some person from Oracle even gave us some insight on when to expect APEX 4.1, but I won't repeat the schedule, because he actually was not allowed to say that (but if you are really interested, I already tweeted about that...).
After lunch I chaired Anthony Ashton's session about "Practical Oracle 11g XML from a developer’s perspective". It contained a thorough explanation of the difference in the deprecated and new ways to handle and query the XL stuff in an Oracle Database. Also there is some open source stuff they created out there for creating PDF's and Reports called FoxOpen. If you have some time, you might want to check it out!
Then I prepared and ran my session about "Creating a subzero dashboard Plugin for APEX with Google Visualizations" - probably one of the longest titles around. Went pretty well I think. I thought I ended exactly on time, but afterwards I realized I ended exactly 5 minutes late... That's the consequence of not having a person charing your session...
The last session of the day was by Iloon Ellen called "Security within Application Express". Good content that emphasizes that you need to think about your security thoroughly. APEX in itself is secure, but developers can make every application insecure!
After some drinks in the exhibition hall we went to the ACE Dinner where we had some good Indian food and I had nice talks with my co-eaters: Sten Vesterli, James Morle and Dave Kurtz. 

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 o...

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 ...

Refresh selected row(s) in an Interactive Grid

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...