Skip to main content

ODTUG: Thursday and the day after...

The last day of this great conference had "only" three presentation slots. The first one I attended, but honestly I didn't pay that much of an attention. I was writing my previous post at that time and I was rather familiar with the subject "Forms to APEX conversion". And I totally agree with the conclusions: Converting simple Forms is easy, but the more complex the Forms, the more work it will take to convert it to APEX!
The second one was called "APEX Stimulus Package". In fact it was more or less a list of things you have to consider to improve the performance of your APEX application - also due to the fact that most demo's didn't work because of a failing internet connection. 
To name some of the tips: Reduce images sizes and use png instead of gif or jpg; check the Apache log for errors and resolve them; add a favicon.ico; watch out with pagination schemes; tune your Page 0 processes; use Page and Region caching where appropriate; minify javascipt and css files; externalize javascript and css files; refactor PL/SQL etc. Some of the tips where obvious, some of them quite useful.
The last one of this week was rather cool. Roy McLean showed how to use Oracle Data Mining in combination with APEX. I never used the Data Mining stuff before, and you might need a degree in maths to use it properly, but the things you can do are rather amazing. For instance you can predict what probably will happen. As an example Roy showed a sort of Helpdesk application where a call was assigned to a certain (pool of) engineers by the text that you entered when describing the problem!
After the show was over I paid a visit to Obama's house, the Washington Monument and checked out the West side of The Mall.
The day after. Friday, I had until 10PM before my flight was leaving, so I visited the Capitol and "did" the East side of The Mall. The weather was fine (cooler than at home!) and it was good fun.
As in previous years I liked ODTUG very much - the best conference in the world. Hope to be there again next year in Long Beach, California.
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 …