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

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report. That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

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