Skip to main content

How attending #Kscope13 can change your life ...

Wow. Doesn't that sound dramatic? It sure does. But in a weird way it also might come true - as I have experienced in the past.
The first Kscope conference I attended was five years ago. And purely by coincidence that was in New Orleans as well! That first year I met all the people I knew from the forums, blogs etc. I had never met one of them before in real life. But due to the relatively small size of the conference and the specific open "Kscope culture" (you can just step up to anyone and start talking!), getting in touch with whoever you like is quite easy. So contacting the "guru's"  - as I saw those people back then, I know better know; now they're all "just" friends - has never been easier!

And what did that bring me?
  • After that Kscope I focussed more on sharing my knowledge by blogging, answering questions o the OTN Forum and presenting.
  • After a few years Oracle rewarded my efforts with an ACE award (and I got an assignment as ACE Director some time later).
  • I wrote a chapter in the Expert Oracle Application Express book - all the authors I have met at ... Kscope.
  • I wrote (the major part) of the APEX for Mobile Web Applications book - what all started by someone I met at ... Kscope.
  • Currently I run the Dutch branch of the APEX Evangelists company. The two founders I met at ... Kscope.

Thus without Kscope, I would have never
  • started sharing my knowledge in the way I did since then.
  • become an Oracle ACE (or ACE Director).
  • written a chapter in an "Expert" book - and certainly not a whole book!
  • started a company of my own.

In short, attending Kscope did have an enormous effect on my business and personal life. And obviously for the better!

So if you have never attended a Kscope conference before (or if you have!), come to New Orleans and join us! But be aware it might change your life .... 





(picture from http://diane-millsap.blogspot.nl/)
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…