OOW Suggest-a-Session : Top Voted Sessions

During the period the Suggest-a-Session for Oracle Open World 2011 on Oracle Mix is open, you can't see the rank of the (or your!) proposal. Only by accessing every proposal and writing down the number of votes, it is possible to get an idea of the rank of a proposed session. This is quite a cumbersome exercise...so why not automate this? Heavily inspired by Wilfred van der Deijl, who wrote a Java program to do that, I created a similar functionality using just the Oracle Database. Who needs Java after all ;-)
The first set up requires setting the ACL right for using utl_http. Next I had to import the certificate Oracle is using for that site into the Oracle Wallet Manager and then create a function that retrieves all proposals and filters the title, presenter and the number of votes. This takes a while, so I dumped the results in a table.
Next I uploaded the results to my workspace on apex.oracle.com (couldn't run the procedure from that site as the ACL there prevents the use of utl_http) and created a Report and a Chart on top of it. So now you can see your rank (I will - try to - update the data every day).

The link to the page is : http://apex.oracle.com/pls/apex/f?p=41715:80
As you can see the session Marco and I proposed still needs some votes, so when you like this overview, please vote for our session as a "thank you": https://mix.oracle.com/events/oow11/proposals/10930-xfiles-the-apex-4-version-the-truth-is-in-there !

Comments

Emre Baransel said…

That will absolutely make my life easier :)) Thanks a lot.

1:33 pm

Kyle Hailey said…

awesome relief to a cumbersome interface - thanks !
Gave you guys a vote.
I hand made a list of presentations from Oracle Oaktable folks:
Oaktable sessions on Oracle Mix

10:05 pm

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

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

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

Roels Blog

Search This Blog