Skip to main content

OOW 2009 : Tuesday

This day started easy by skipping the keynotes. So the first session I attended was at 11:30, called The Life of a Query in which the presenter revealed the details on the internal processing of the Oracle database.
Next was Giving your Application Express a Web 2.0 Facelift. Not that many new things, but Raj is always very entertaining to watch. The most interesting thing I saw was a new prototype of the APEX Developer page on Patrick Wolfs laptop: Instead of the current Page Definition view (with Page, Regions, Items, Processes and so on), the same information was presented in an DHTMLX tree view! Patrick showed how you can easily re-order Items, copy buttons etc by just dragging them around in the tree. And on every object you can do a right mouse click that would present the actions you can do with that object. It looked very slick! We shortly discussed whether or not you should expand that tree with one level (Page) or even two (Application), to make it even easier to copy and move Pages or Regions around. Imagine something like the tree view of your application in Oracle Designer - but then better looking. I guess this prototype won't make it to APEX 4.0, but it shows that the product is still evolving - even after APEX 4.0!
After that Understanding Real Application Clusters for Developers was on the program - I guess using Dummies instead of Developers was to offensive. However it was a reasonable good overview about RAC, but didn't associate about anything that a developer might have to do with it. And the presenter ran seriously out of time....
The last one of the day: Oracle Performance by Design. A presentation full of half truths and generalizations. So no further comments....
In thee evening there were three meet-ups to attend: The Blogger MeetUp, Benelux Cocktail Party and the APEX MeetUp. I had to pick and did the first and the last. Alex G., who organized the Blogger thing this year, also introduced a nice competition. He/she with the most names on their new T-shirt (with the text "I met more bloggers than you"), would win a netbook! So there was a lot of signing going on! Good job, thank you Alex!
And of course, at the APEX meetup al the usual suspects where there. And - as every time - it was really nice to meat each other again!
Post a Comment

Popular posts from this blog

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

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 worse) while you…

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…