Skip to main content

ODTUG Kaleidoscope 2008 : Day 3 - Experts Day

Building Advanced Tabular Forms was the first subject of the day. In APEX you can build tabular forms (a multi record update form) using a wizard or manually (with the APEX_ITEM API and processing with the APEX_APPLICATION API. Another option is using a collection which gives you full control on the processing - like distributing your data over multiple tables.

After that one Dimitri Gielis presented on Creating Advanced Charts with APEX. He showed the audience what you can do using the charting options of APEX. Impressive!

Next was the Oracle APEX Developer of the Year 2007, Patrick Wolf. His main message is that you can speed up your development process (even further!) when you use the right third party tools. The tools you can't do without as an APEX developer are - apart from Firefox itself:
  • Firebug - a great extension on Firefox
  • Web Developer - another Firefox extension
  • YSlow - a performance monitor, again an Firefox extension
  • Live HTTP Header - to track traffic between the browser and from server, again Firefox
  • APEX Developer Plugin - An extension on APEX that Patrick built, to make your live (even) more easy
  • APEX Essentials - An APEX application to check the quality of your APEX application, free, adaptable and extendible, created by Patrick
  • jquery - A great Javascript pack, this may be included in the next version of APEX
  • APEXLib Framework - A framework, by Patrick, that reduces the writing of code even more
I will report on the presentations of Anton Nielsen and Carl Backstrom later (because I'm at the airport right now and have to get into the plane soon).

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…