Skip to main content


After yesterdays Blogger Meetup it was hard to start the day...
The first session of the day was Sue Harper's talk on SQL Developer Latest Features. She mainly focussed on the new / enhanced features of version 1.5, that will be production somewhere (early?) 2008. To name some new features : external authentication (OPS$ users), browsing queues and Java, schema differences and schema copy, recall filters and a flashback query tab, formatter enhancements, your own code templates and drill down reports. With very new version SQL Developer looks more like the current TOAD version ;-).

After that I visited a session about Building Rich UI with APEX and AJAX. It was pretty impressive what you can do with a combination of APEX and AJAX (look at The presenter also showed the use of widgets of the jQuery UI library like an accordion and a fancy date picker (

The next session about the Roadmap for legacy system migration I chaired. A solution for the upgrade to Designer / Developer 10g was presented that can' t compete with our Famous solution! The most interesting part of this presentation was the use of Dataload Classic ( for playback testing (recording actions in the old forms, playing it back in the new ones).

After that one I went to see Grant Ronald on AJAX UI Development with JSF and ADF Faces. The good news is that we don't have to worry about the (complicated) AJAX stuff, because it's all hidden after the new ADF Faces Rich Client UI objects. And they look really great : Accordions, drag and drop etc.

Next on the program was a session on Rules Manager and Expression Filter: a way to let Oracle watch for incoming data conforming a specific where clause. You can use this feature for information distribution or workflow. Sadly to say that it needs a lot of difficult steps to set up.

Last but not least was Steven Davelaar (again chaired by me) enthousiastic as ever telling en demoing JHeadstart. He showed the new (version 10.1.3) features on Security, Dynamic Menu's, Multi Language Support and Flexible Items. The most impressive news is that also for JHeadstart Oracle is working on a Release 11 version - with all the beautiful AJAX features.... As allways it was hard to keep him to the time schedule ;-).

And now off to the ' community focus pubs' .
Post a Comment

Popular posts from this blog

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…

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…

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 …