Skip to main content

OOW 2009 : Wednesday

By
I started off with a good breakfast with my roomies Marco and Jacco. Because there wasn't any interesting session in the first timeslot (or I couldn't find it), I attended the Exhibition Hall - which is mainly the same as previous years. Everyone wants to 'scan your badge' so they can spam you afterwards.
Next there were two sessions I really liked, and - it may or may not be a coincidence - both were 30 minutes 'power sessions'. The first one was by Mark Drake, the Product Manager for XML DB, about Managing XML Content with APEX. Very good job, although having live demo's obviously are a risk...and that's why I like them!
The next one was about Row Level Security / VPD and APEX. The presenter had a good demo and explained the stuff nicely.
I followed the keynote from the OTN Lounge (it is less boring with a beer). It wasn't a surprise anymore that The Governator would attend. Arnold emphasized that technology will deliver the solution for CO2 reduction - he didn't say that technology was also the cause of all kinds of pollution...
Larry's story - the only presentation from Oracle without the safe harbor slide - didn't contain anything astonishing new: Oracle has Linux and VM (that's a three year old story); has an Exadata machine thats an (undefined) number of times faster than the one form IBM (Sunday's news..); My Oracle Support will get better; Fusion Apps are on their way (with demo).
The last real session of the day was Building a Mashup with APEX. The presenter painted out an architecture where you create webservices on your database objects, and consume those in APEX on XE. The reasons for doing so was that
- you don't need a license for XE (that's true, but you do need a license for the underlying database, so that's a non-argument)
- he thought that APEX itself would have a negative impact on the performance of his database (which is obviously also a non-argument, as APEX adds only a very little bit of overhead - and creating extra layers as he suggested will create more overhead)
- the DBA's didn't like the idea for having an 'application in the database': the database is for data, not for applications... (An misconception that some old school DBA's hang on to).

And at night : The Appreciation Event with Aerosmith. And they rocked - especially when you know that Steven Tyler (the leadsinger) is 61!
Labels:

Comments

Louis-Guillaume said…
Hi Roel,

What did you learn during "Managing XML Content with APEX" session?

Thanks for keeping us up to date!

L-G
11:50 pm
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
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
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function
Post a Comment
Read more