Skip to main content

ODTUG: Monday

The day started with the General Session. There the ODTUG Board announced when en where the next Kaleidoscope will be held: At Long Beach, California! From June 26 to 30 2011. And you can even submit papers as from now! There is a link somewhere, and if I'll find it I'll add it to this post. Another remarkable thing was that the number of attendees this year was up with 50% to around 900! So ODTUG grows bigger and bigger every year - and so even getting more important in the Oracle world.
Next - and rather important - was the game...The Netherlands against Slovakia. We saw the match with a couple of other attendees, most of them Dutch, but also some other guys - but all supporting Holland And we won with 2-1, which was great. So in the next match we have to beat Brazil - which will be though!
Back to the stuff we all here for...
The first afternoon session was the "APEX 4.0 Keynote", where Mike showed all the cool new APEX 4.0 features for an interested audience of over 250 people (rough count). Nice to notice that even my name was mentioned when Joel answered a question about upgrading to 4.0: "If your name is not Roel and do not live in The Netherlands, you'll be fine". ..pointing out to a bug a discovered only 15 minutes after 4.0 was released - BTW that bug has been fixed the same day!
For the next hour I was the ambassador for Anjo Kolk's session on "Accessing databases from Google Apps" Completely off the APEX topic, but nevertheless very interesting.There seems to be an App store like marketplace for Google apps - really didn't know that. Anjo showed how to extend a Google spreadsheet by accessing data from a mySQL server using jdbc. An Oracle extension is in the making. You can also get data from your database using import functions.These functions are insecure, but if you want a secure connection - and are willing to pay for it - you can use the Secure Data Connector. That SDC uses tunnelling via the Google Tunnel Servers.He also showed how to query (and update) data in a Google database with the Google feedserver. Getting this working is not that easy, requires some tweaking and modifying XML files, but the result is nice. You can also use PL/SQL functions that return JSON to feed Google Visualizations and show these graphs in iGoogle - and so you create your own dashboards on the web, using real live data from your database!
In the next session, called "APEX; A window to the Oracle Database", Anton Nielsen demoed how to use some cool advanced database features in APEX. Like Oracle Text (with "smart searching"), Analytic functions, Intermedia for images (thumbnail generation, rotation, capturing metadata etc) , external tables and VPD. The key of all this is, if you can do it in the database you can do it in APEX as well!
During the Sundown Sessions - a sort of Q&A session - a lot of good questions where asked and answered. The main announcement was that the APEX Listener was released just that afternoon!
After the reception (more food and drinks), there was a poker game organized in the bar. I joined the hard core players, and managed to end as third (and it actually was my first real poker game ever!), So in the end I got my 20 bucks entrance fee back! It was a lot of fun - and we stayed up until .. let me say ... late.


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…

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 …

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…