Skip to main content

ODTUG: Monday

By
The day started with the General Session. There the ODTUG Board announced when en where the next Kaleidoscope will be held: At Long Beach, California! From June 26 to 30 2011. And you can even submit papers as from now! There is a link somewhere, and if I'll find it I'll add it to this post. Another remarkable thing was that the number of attendees this year was up with 50% to around 900! So ODTUG grows bigger and bigger every year - and so even getting more important in the Oracle world.
Next - and rather important - was the game...The Netherlands against Slovakia. We saw the match with a couple of other attendees, most of them Dutch, but also some other guys - but all supporting Holland And we won with 2-1, which was great. So in the next match we have to beat Brazil - which will be though!
Back to the stuff we all here for...
The first afternoon session was the "APEX 4.0 Keynote", where Mike showed all the cool new APEX 4.0 features for an interested audience of over 250 people (rough count). Nice to notice that even my name was mentioned when Joel answered a question about upgrading to 4.0: "If your name is not Roel and do not live in The Netherlands, you'll be fine". ..pointing out to a bug a discovered only 15 minutes after 4.0 was released - BTW that bug has been fixed the same day!
For the next hour I was the ambassador for Anjo Kolk's session on "Accessing databases from Google Apps" Completely off the APEX topic, but nevertheless very interesting.There seems to be an App store like marketplace for Google apps - really didn't know that. Anjo showed how to extend a Google spreadsheet by accessing data from a mySQL server using jdbc. An Oracle extension is in the making. You can also get data from your database using import functions.These functions are insecure, but if you want a secure connection - and are willing to pay for it - you can use the Secure Data Connector. That SDC uses tunnelling via the Google Tunnel Servers.He also showed how to query (and update) data in a Google database with the Google feedserver. Getting this working is not that easy, requires some tweaking and modifying XML files, but the result is nice. You can also use PL/SQL functions that return JSON to feed Google Visualizations and show these graphs in iGoogle - and so you create your own dashboards on the web, using real live data from your database!
In the next session, called "APEX; A window to the Oracle Database", Anton Nielsen demoed how to use some cool advanced database features in APEX. Like Oracle Text (with "smart searching"), Analytic functions, Intermedia for images (thumbnail generation, rotation, capturing metadata etc) , external tables and VPD. The key of all this is, if you can do it in the database you can do it in APEX as well!
During the Sundown Sessions - a sort of Q&A session - a lot of good questions where asked and answered. The main announcement was that the APEX Listener was released just that afternoon!
After the reception (more food and drinks), there was a poker game organized in the bar. I joined the hard core players, and managed to end as third (and it actually was my first real poker game ever!), So in the end I got my 20 bucks entrance fee back! It was a lot of fun - and we stayed up until .. let me say ... late.
Labels:
Location: Woodley Park, DC, USA

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 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