Skip to main content

UKOUG 2010 Recap - Wednesday

Wednesday I started late, because I skipped the first session to prepare for my second one "Tales from a Parallel Universe: Using 11gR2’s Edition Based Redefinitions". Went also pretty good as well I think, ended nice on time - even, again, with a session chair. And I received some really positive feedback from people like John King and Christian Antognini. Thanks guys!
Then there was a funny debate kind of session between Tony Hasler and Jonathan Lewis about "Does Oracle ignore hints?". In the end it was all about semantics...if you discard bugs, poor or wrong documentation and more or less hidden features and unexpected optimizer processes, Oracle never ignores your hint (which in fact is more a 'directive' than a hint) - otherwise you might say that Oracle actually does  ignore your hint.
After lunch - instead of the good hot lunches we received a school-like lunch bag this time - I chaired my second session : "Edition-Based Redefinition: Testing Live Application Upgrades (Without Actually Being Live)". Because I already was familiar with the subject at hand, there wasn't very much new stuff in there - but I am always curious to see if I missed someting in my own presentation...
The last session of the event I attended was "Still using ratios" by my colleague Piet de Visser. Due to the worst time slot of the week - and the weather -  there were only a few attendees (around 10). The content was good though. He should have the chance to redo that presentation on a better time!
Then the people that didn't left Birmingham (or couldn't) all winded down in All Bar One and O'Neills for some final drinks and talks.
All in all again a good conference qua content and attendees. Always good to catch up with people you only met a couple of times a year during this kind of events. Hope everybody made it back home eventually and already looking forward to the 2011 edition of the conference!
1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…