Skip to main content

ORCAN event

By
Yesterday I attended an event organised by the Swedish Oracle User Group (ORCAN). They picked a real nice venue for this meeting: the top floor (54) of the Turning Torso. From this top floor you have a stunning view over the Oresund (all the way to Copenhagen) and Malmö and it's surroundings. Might be a little bit distracting from the presentations, but nevertheless...
There were two concurrent presentations. The first one I attended was by Moren Egan about Edition Based Redefinitions. As I presented about the same subject at OOW and UKOUG, I was just curious about how he would present this material. More SQL*Plus oriented as I did it, but I think the message came across just fine. The second one was by Randolf Geist, called "Advanced Oracle Troubleshooting". In fact it was just the first half (the second half was after lunch). Although I could grasp most of he said, some details were a little bit over my head. So I skipped the second part and went to SQL Developer New Features by Sue Harper. I was already familiar with most of the features, but it's still worthwhile to renew your insight about this product. It is growing with every release!
Then it was my turn wih APEX 4 New Features. To my surprise 75% of the audience had no experience at all with APEX - so all features are new to them! But I emphasized and spent most of the time demoing the cool Dynamic Actions and Plug-ins. Just to show how you can create stunning results with almost no coding! After a short coffee break I presented about Charts & Dashboards. This time I had alomst all attendees in my class, as the "other side" only had 4 (sorry Sten). All went pretty well I think, but I have to admit, doing two presentations back to back is a little bit exhausting.
Then it was time to leave for dinner in the center of Malmö. When I got my jacket I noticed my pockets were empty - and I was pretty sure I left my car keys and phone in there (which isn't that smart, I have to admit)! So a little panic broke out. We contacted the reception, searched the whole place - but nothing found. But then I noticed that there was something else missing from my jacket: It had just the Oracle logo, and mine had Oracle ACE Director logo! So it wasn't mine! A quick thought whose jacket it could be...and it had to be Sten Vesterli. And Sten was on his way to Copenhagen... We phoned him, but got his voice mail. So we went to the restaurant...and there was Sten with my jacket. While walking to the station he noticed there was a phone in his jacket (or my jacket) and another one in his pocket. So he also concluded he had taken the wrong one - and decided to go to the restaurant to exchange jackets. A total relief for me. Thanks Sten - not for taking the wrong jacket, but for returning it ;-) !
We had a nice dinner outside on the square. This little square is packed with restaurants and everyone is sitting outside. So they have a lot of heaters (and I mean really a lot!) and blankets for everyone. So I think global heating is for a major part caused by the Swedish... ;-)
All in all a nice event and I am looking forward to the next one!
Labels:
Location: Malmö Municipality, Sweden

Comments

Learco Brizzi said…
Sounds like a nice day. I'll hope APEX will be as popular in Sweden as it is here in Holland :-)
9:40 am
linlasj said…
It is starting to evolve. I do not fully understand why there is such hesitation.
3:32 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 o...
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