Skip to main content

#APEXinDublin

Last Tuesday CampusIT - in cooperation with Oracle - organized the first APEX event in Ireland. Around 50 people from around the country visited the O'Callaghan Alexander hotel for a series of five presentations around APEX (done by the four presenters on the picture). First on was Dimitri with his "Mastering an APEX Page" presentation - always a success. I was om next doing my "APEX and Forms Integration" presentation and demo.
After a - very good ! - lunch Bary McGillin from Oracle (from the SQL Developer Dev Team) was substituting Hilary Farell (from the APEX Dev Team), who couldn't make it - probably very busy with the last loose ends of APEX 4.0. After the APEX 4.0 presentation Barry did a presentation on SQL Developer 2.1.1.  But he also did a demo on the brand new 3.0 release. And as you might expect this release includes many new features and enhancements. Some of these features are aimed at the DBA, like changing Oracle parameters on the fly, adding datafiles and even starting and stopping instances. Other new things are more for Developers, like another way of browsing users and objects (more TOAD-style) and even a Tuning Advisor!
An early adopter of this new version should be available somewhere in the summer, while the official release is planned midst September (read "Oracle Open World"). All the usual disclaimers applied of course!
The slides of the presentations are available from the bottom of this page.
Post a Comment

Popular posts from this blog

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 …

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…

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…