Skip to main content

Developer Choice Awards Update: Let the judging begin!

After a one week extension for the nominations period, we have now closed nominations for the first-ever round of Oracle Database Developer Choice Awards.

We have a total of 75 nominations across five categories (SQL, PL/SQL, Application Express, Database Design and ORDS). That's quite a healthy number and we look forward to the judges now winnowing that list down to a set of finalists in each group.

Judges? What judges? Isn't Oracle simply going to decide who the finalists - and then winners - will be?

NO WAY.

These are developer choice awards. By this we mean that our users decide the finalists and then vote among the finalists to determine the winners of the awards.

We've set up a panel of judges for each category. Each panel consists of four ACEs and/or ACE Directors, plus one Oracle employee. For example, I am on the PL/SQL panel (surprise!).

And now you are probably wondering: so who are the other PL/SQL judges? And the judges on the other panels?

Ha. You expect us to give away all our secrets? :-)

No, seriously, we are going to release the names of the judges after we publish our lists of finalists, and popular voting begins.


Otherwise, who knows? Judges might start receiving boxes of chocolates flown in by Amazon drones within ONE HOUR of being ordered by a nominee or that nominee's devoted significant other. We can't allow that.


But I do like to recognize initiative. So if you want to influence votes via chocolate, make sure they have nuts in them (see above photo), and send them straight to:

Steven Feuerstein
Chicago, Illinois
Planet Earth

We will announce the finalists on 15 September, and voting will commence until 15 October.

We will then announce the winners of the 2015 Oracle Database Developer Choice Awards at the second annual YesSQL celebration at Oracle Open World 2015.

Comments

  1. amarjotAugust 26, 2015 at 1:45 AM

    Hi,

    Sorry i am late.. is there any chance so that i can participate in this competition?

    ReplyDelete
  2. Steven FeuersteinAugust 26, 2015 at 2:34 AM

    Sorry, amarjot, but it is too late for this year. There is always, however, next year!

    ReplyDelete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more