Skip to main content

OOW 2009 : Monday

Still suffering from the jet lag I woke up at 6 AM today. Due to all kinds of other 'obligations' I only attended one session today about "How to get 10x improvement of your PL/SQL Application performance time". And that one was all about TimesTen (a.k.a. IMDB - In Memory Database Cache). The session started with a small - alas pre-recorded - demo that indeed showed a 10x performance benefit. But before you all start to move all your applications to TimesTen, be aware that there are 'some' limitations:
- Not all standard PL/SQL packages are available in TimesTen
- You can't call PL/SQL from SQL
- You can't use triggers in TimesTen
- You can't join between tables in TimesTen and the 'real' database
So due to this limitations, you can't run all PL/SQL applications (like APEX!) in a TimesTen database. However it would be extremely cool if you could use TimesTen for APEX (imagine APEX running 10x faster!). So maybe somewhere in the future, but not with the current release.
Next a had a (long) lunch with 16 Logica attendees from all over the world, very well organized by my US colleagues.
After that, I headed to the demogrounds, to take a close look at APEX 4.0. Mark and Anthony where so kind to show me a (private) deep dive into the new features, like enhanced tabular forms (with field validations), Team Development (a sort of integrated packaged application for registering enhancements and bugs, assignments etc), Dynamic Actions and Plug-Ins. This all looks very promising and opens up a whole new set of functionality, that would require a lot of handcraft in the current version. APEX 4.0 is (still) planned for production somewhere in 2010 (I hope it will be in the first quarter!).
Next I went to a hotel where a bus picked me up for a ride to the HP Pavilion in San Jose to see my first ice hockey game: San Jose Sharks v.s Phoenix Coyotes. Very nice to see that sport live in an American ambiance! Thanks to my French colleagues for organizing this!
At the moment of writing this - Tuesday morning - it is very rainy and windy in San Francisco. Rather different from my previous visits at OOW, where the sun always shined... Time to get my umbrella!

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…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

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 …