Skip to main content

OOW2010 Wednesday

By
Alas I missed the Benelux cocktail part last night, because the dinner took somewhat longer than expected. The dinner was extremely good though.
This day started with a session by John Scott Spendolini about "Recovering from APEX mistakes" - I didn't know they existed but nevertheless. Good session on how to undo changes you've made, debugging etc. The next one was by Marco Gralike on XML-DB (what else could it be?). Good, detailed info with some nice examples. Not all demos worked like he meant to, but that's the price you pay when you mess with them the night before! Especially the event firing mechanism when you drop a file in an XML folder are very cool! Marco, we definitely need those for our ODTUG presentation!
Then Raj did a presentation on collections, enthusiastic and dynamic us usual. But also his deno didn't turn out as expected. The best take away from this session was the idea to create views on top of your collections, so you can maintain the code more easy.
Larry's Wednesday's keynote was rather disappointing. No new announcements, just a recap of the things announced earlier this week. And that took rather long, so I missed the Fusion Apps demo as I headed for a session on EBR by Boeing. They already really use it in their mission critical business applications. By implementing EBR they managed to reduce the outage for an application upgrade from 9 hours to less then 1! Very impressive.
Next was the Blogger Meetup. Always a good opportunity to match faces with names. And the. Off to the Appreciation event! It was definitely more crowded than last year, with long lines for the food. And some good bands too! Don Henley may look somewhat older, but his voice still sounds like 30 years ago. And the Black Eyed Peas surprised me, with a very good show. This is the first time I saw the whole crowded joining the band: All yo part people in da house, say yoo-hoo.
I got a bus back around 12, because I need a relative good night sleep for my session tomorrow. I am curious how many people will show up, as I heard a lot of people saying they'll leave on Thursday....
Labels:

Comments

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