Skip to main content

UKOUG 2010 Recap - Tuesday

Tuesday started of with a two hour Masterclass by Cary Millsap "Thinking clearly about performance". A really great session that explained clearly what performance actually is (so the content covered the title). Using with a lot of nice stories, examples and analogies Cary has the ability to explain stuff that seems difficult in a way everybody can understand. If you haven't seen this one, it is really a must see if you have the chance!
Because the next session on my agenda was shifted to another place and time a had some time to walk through my own presentation for that afternoon before attending the APEX Roundtable. A nice Q&A about what all APEX stuff. Some person from Oracle even gave us some insight on when to expect APEX 4.1, but I won't repeat the schedule, because he actually was not allowed to say that (but if you are really interested, I already tweeted about that...).
After lunch I chaired Anthony Ashton's session about "Practical Oracle 11g XML from a developer’s perspective". It contained a thorough explanation of the difference in the deprecated and new ways to handle and query the XL stuff in an Oracle Database. Also there is some open source stuff they created out there for creating PDF's and Reports called FoxOpen. If you have some time, you might want to check it out!
Then I prepared and ran my session about "Creating a subzero dashboard Plugin for APEX with Google Visualizations" - probably one of the longest titles around. Went pretty well I think. I thought I ended exactly on time, but afterwards I realized I ended exactly 5 minutes late... That's the consequence of not having a person charing your session...
The last session of the day was by Iloon Ellen called "Security within Application Express". Good content that emphasizes that you need to think about your security thoroughly. APEX in itself is secure, but developers can make every application insecure!
After some drinks in the exhibition hall we went to the ACE Dinner where we had some good Indian food and I had nice talks with my co-eaters: Sten Vesterli, James Morle and Dave Kurtz. 
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 …