Skip to main content

The saddest post

This is probably the saddest post I'll ever write. Just as many of you, today I also received the message that Carl Backstrom died in a tragic car accident last weekend. I met Carl on two events this year: ODTUG and OOW. He was a very nice and energetic guy to talk to, open to everyone who wants to talk to him.
Apart from the neverending fly whiskeys at the the bar in the hotel lobby and the visits to some Bourbon Street bars, I guess a lot of APEX'ers will remember him by his presentation on last ODTUG. Dan McGhan, as an ambassodor for that session, introduced Carl as The UI God. And Carl did his most nervous presentation ever I guess. He struggled with the mic because his hands were too shaky to get the clip fixed the right way. And everybody wondered why he could be so nervous as he knew so much and we knew so little. But that was typically to Carl: Although he knew everything about APEX, Javascript, jQuery and JSON, he still was a regular guy, happy to share his knowledge with others (but rather on a one-to-one basis than in front of a somewhat larger audience).
We will miss him a lot....
My condolences to his family, friends and colleagues.
1 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…