Skip to main content

OOW 2009 : Thursday and wrap up

The day started easy: The first session had similar content as the last one of yesterday - which I didn't like too much - and the second one got cancelled. So a late start, what was fairly convenient because of yesterday's party...
The first one was by Arup Nanda about 11g New Features for DBA's. Since 11g is already 'old school', I didn't learned that much: physical / logical / snapshot standby databases (quite handy for testing in a real production environment, performing rolling upgrades and reporting); partition by reference (where you can easily keep master and detail data in the same partition) etc. I was hoping for more R2 stuff, but maybe it is just to early as that version was released just a couple of weeks ago.
The second one was all about Data Security. There are so many features and options regarding that subject. To name a few: VPD, FGA, Encryption, Data Masking, Advanced Security, Audit Vault, Database Vault, Label Security, Secure Backup.... I think it is time for a new SQL command: "alter database set security = high".
The last session of this years OpenWorld was done by Rich Niemiec. He is a great entertainer (throwing candy, bars, chips etc. in the audience, lots of funny stories) and managed to put over 200 slides in 1.5 hour - what was only half an hour over time. This session was also called "11g New Features" - but this time not only for DBA's. And again, not many things that I haven't heard before.
That night Andreas surprised his housemates with a real gourmet dinner (with bison steak). And that was a really good closure of what should become a tradition: the Holland ACE House! Thank you Andreas, Jacco and Marko for your great company this week. And of course a special big THANK YOU for Anjo: He made this all possible!

Typed on my iPod in a shaking plane...
1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …