Skip to main content

Tom Kyte's prequel to Guru4Pro

Yesterday over 100 Pro's attended Guru Tom's session on '11 Things about 11g'. But in the hours before that session a small number (about 18) of persons had the honor of listening and discussing with the master himself. As a guide he used an extensive version of his 'Worst Practices' presentation. During - and after - the presentation there was a lot more Q&A than I've experienced in regular sessions - of course due to the small scale of this session.
On a question about the new features and enhancements of 11gR2 Tom told that there will be no export functionality anymore in R2 (import will be available though). For moving data from one instance to another you should use datapump or SQL Developer or APEX. Also he explained a little more about the Online Application Upgrade. This feature will use invisible indexes, cross edition triggers and (a maximum of) two versions of PL/SQL programs and views (tables are not versionable). It sounds like it is not a black box feature, but needs some programming to get things working. By the way, in 11gR1 this functionality is already available and you can turn it on using some hidden initialization parameter (I don't know which). You can see the column edition_name is there in the all_objects view..... 11gR2 is expected to be available in 2009Q1!
For all APEX developers: Tom, as expected from a database man, is truly an APEX supporter - he mentions the power of APEX a lot during his presentations!

Comments

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…