Skip to main content

My Oracle Open World 2006 Schedule

As other bloggers I also publish my OOW2006 schedule. It was hard to choose between 70 parallel sessions, but IMHO I succeeded in planning a nice schedule:

I'll arrive on Friday, so on Saturday I have one day to recover from the jetlag and visit some interesting sites in San Francisco (also plan a schedule for this touristic part of my visit).

Sunday
ODTUG Oracle Developer Suite (Forms and Reports) Special Interest Group Meeting
I am a user of some of the ODTUG mailing lists. I hope to meet a couple of the people I read posts from for a couple of years.
IOUG Oracle Application Express (APEX) Special Interest Group Meeting
There is - sadly - very little about APEX during OOW and I'll plan to visit most of the sessions with APEX in the title.
Build a Dynamic Menu Framework with Oracle Application Express
And this is also one of the APEX-sessions

Monday
Developing PL/SQL Programs, Using Automated Unit Testing
by my English colleague Andrew Clarke - I'm looking forwar to meet him and listen to what he has to tell about this subject.
Database Worst Practices
by Tom Kyte, so always interesting!
Unleashing the Power of Oracle Streams
I planned to visit more sessions about Streams, because I don't know anything about the subject, apart from a short description - and that sounds interesting enough.

Tuesday
Using Oracle Advanced Queues to Facilitate Near-Real-Time Integration
Queues, Streams - I'd like to know more about thta!
Developing Powerful Oracle Business Intelligence Beans in Oracle Forms
I've used Forms for years, but never used BI beans.
Oracle XML Publisher: Enterprise Reporting and Delivery Platform
XML Publisher is antother new feature. As far as I see it, it coulde be the future replacement of Oracle Reports and/or Oracle Discoverer.

And in the evening I'll visit the 2nd Annual Open World Blogger Meetup

Wednesday
Customer Case Study: XML Publisher Live with all the Bells and Whistles
More about XML Publisher
Data Design Reviews: Using Extreme Humiliation to Ensure Quality Data Models
The title sounds so tempting...
Dynamic SQL in a Dynamic World
How dynamic can or should we be?

Thursday
Implementing Oracle Streams Replication
More on Streams..
Test-Driven Development in the World of PL/SQL
by Steven Feuerstein.. I've visited a day long session by Steven last year and this subject was just shortly mentioned then.
Oracle JDeveloper 10g with Oracle ADF Faces and Oracle JHeadstart: Is it Oracle Forms Yet?
Productivity is so important in our business...
Oracle Discoverer Future: Protect, Extend, Integrate
Were is Discoverer heading to...

Friday
One more day to visit the touristic highlights of SF.

Saturday
Flying back...

I'm looking forward to all of this! I've never visited a huge event like this (over 40.000 visitors), - apart form a soccer game or a rock festival....

Comments

Popular posts from this blog

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

Filtering in the APEX Interactive Grid

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

Stop using validations for checking constraints !

 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