Skip to main content

Riga Dev Day 2015

While waiting at the airport for my plane back to Amsterdam, I have some time to write down my experiences of the last few days in Riga.
After arriving in the hotel, I walked to the old part of town and strolled around. The old part looks very medieval (it is - so no surprises there) with cobblestone streets, old houses and very few cars. Nice!
Then back to hotel, in time for the "official" speaker tour. With a small bus we toured around town for 45 minutes and we walked the old town (again) for another 45 minutes - but now including some stories about the buildings we saw. It was rather cold, so I was quite happy when we got back to the bus and on to the restaurant for the speakers dinner. All very well organised "extra's". Thanks guys!

The event itself was held in a movie theatre in a mall. About 400 attendees filled up the large keynote room pretty quickly. The nice thing about this setting is that the screens are huge and excellent: I've never seen my presentation that big! Also the fact that some people were eating popcorn during the presentations added something to the "movie effect". I would like to see more events in venues like this!
As they conference was a combination of three user groups (Google Dev, Java and Oracle) it was very easy to attend a session that is way out of my comfort zone. So I did a few sessions on Android, Node and REST API's. Just to see something different. My own session was well attended with around 50 people. Just a few of them were actual APEX Developers, the rest was DBA, PL/SQL - or out of their Google/Java comfort zone.
After the event we grabbed a cab bak to the hotel to drop off our bags and a cab back into the old town for the afterparty. Music, some food and lots of drinks. It was fun. Afterwards a cab back to to hotel for the after-afterparty. 
This morning after checking out, I walked back into the old city to check out the parts I haven't seen yet, like the big market halls. Then taxi back to the airport...

All in all a great event, very well organised. Thanks for inviting me - and thanks to the Oracle ACE program for the support !
Post a Comment

Popular posts from this blog

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…

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 …