Skip to main content

Sneak preview for Kscope14 !

It has been a while, but this year AMIS and SMART4APEX are organizing an ODTUG KScope Preview event together. This event will be held on Thursday, June 12th at the AMIS offices in Nieuwegein.
This year the annual ODTUG - Oracle Developer Tools User Group - event takes place in Seattle, from June 22 to 26. Alas not everyone has the chance to join this event. And therefore AMIS and SMART4APEX have joined forces and offer the opportunity to attend some of KScope’s presentations. A number of presenters from Europe will run a final try out of their presentations during this preview event.
During the event you will have the choice of three presentations in three streams: APEX, Database Development and ADF.Click on the agenda for the list of sessions and their abstracts.

To make sure there's enough place (and food ! and drinks !) for everyone : Click here to register.

And, yes, we are well aware the World Championships are starting that very same night. But luckily that first game starts at 10PM. So you can visit both this Kscope Preview and watch Brazil - Croatia when you get home!

Hope to see you in Nieuwegein on the 12th of June ...

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…