Skip to main content

ODTUG: Monday

The day started with the General Session. There the ODTUG Board announced when en where the next Kaleidoscope will be held: At Long Beach, California! From June 26 to 30 2011. And you can even submit papers as from now! There is a link somewhere, and if I'll find it I'll add it to this post. Another remarkable thing was that the number of attendees this year was up with 50% to around 900! So ODTUG grows bigger and bigger every year - and so even getting more important in the Oracle world.
Next - and rather important - was the game...The Netherlands against Slovakia. We saw the match with a couple of other attendees, most of them Dutch, but also some other guys - but all supporting Holland And we won with 2-1, which was great. So in the next match we have to beat Brazil - which will be though!
Back to the stuff we all here for...
The first afternoon session was the "APEX 4.0 Keynote", where Mike showed all the cool new APEX 4.0 features for an interested audience of over 250 people (rough count). Nice to notice that even my name was mentioned when Joel answered a question about upgrading to 4.0: "If your name is not Roel and do not live in The Netherlands, you'll be fine". ..pointing out to a bug a discovered only 15 minutes after 4.0 was released - BTW that bug has been fixed the same day!
For the next hour I was the ambassador for Anjo Kolk's session on "Accessing databases from Google Apps" Completely off the APEX topic, but nevertheless very interesting.There seems to be an App store like marketplace for Google apps - really didn't know that. Anjo showed how to extend a Google spreadsheet by accessing data from a mySQL server using jdbc. An Oracle extension is in the making. You can also get data from your database using import functions.These functions are insecure, but if you want a secure connection - and are willing to pay for it - you can use the Secure Data Connector. That SDC uses tunnelling via the Google Tunnel Servers.He also showed how to query (and update) data in a Google database with the Google feedserver. Getting this working is not that easy, requires some tweaking and modifying XML files, but the result is nice. You can also use PL/SQL functions that return JSON to feed Google Visualizations and show these graphs in iGoogle - and so you create your own dashboards on the web, using real live data from your database!
In the next session, called "APEX; A window to the Oracle Database", Anton Nielsen demoed how to use some cool advanced database features in APEX. Like Oracle Text (with "smart searching"), Analytic functions, Intermedia for images (thumbnail generation, rotation, capturing metadata etc) , external tables and VPD. The key of all this is, if you can do it in the database you can do it in APEX as well!
During the Sundown Sessions - a sort of Q&A session - a lot of good questions where asked and answered. The main announcement was that the APEX Listener was released just that afternoon!
After the reception (more food and drinks), there was a poker game organized in the bar. I joined the hard core players, and managed to end as third (and it actually was my first real poker game ever!), So in the end I got my 20 bucks entrance fee back! It was a lot of fun - and we stayed up until .. let me say ... late.
Post a 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…