Skip to main content

Oracle Database Developer Choice Awards: the voting has begun!

The Oracle Database Developer Choice Awards celebrate and recognize technical expertise and contributions in the Oracle Database community. As longtime and new users of Oracle Database move to the Cloud and take advantage of this exciting new architecture, community experts will play a critical role in helping them succeed.

Panels of (mostly) Oracle ACE judges have now selected their finalists, and the time for public voting has begun! From 15 September to 15 October, we call on all members of the Oracle Database developer community to check out the finalists for each of these categories and vote for those you think deserve worldwide recognition for their work.

You can vote for as many finalists as you like, but you can register only one vote per finalist (even those of us living in Chicago).

And if you would like to help us generate buzz for the awards program via Twitter and other social media platforms, please use the #odevchoice hashtag.

Congratulations to all our finalists! Even if you do not take home an award, making it onto this list is a substantial achievement in and of itself.

SQL Finalists
  • Stew Ashton
  • Justin Cave
  • Kim Berg Hansen
  • Sayan Malashinov
  • Emrah Mete
  • Matthias Rogel
  • Erik van Roon
  • Sean Stuber
PL/SQL Finalists
  • Patrick Barel
  • Adrian Billington
  • Morten Braten
  • Bill Coulam
  • Kim Berg Hansen
  • Sean Stuber
  • Roger Troller
Oracle REST Data Services Finalists
  • Dietmar Aust
  • Morten Braten
  • Dimitri Gielis
  • Anton Nielsen
  • Kiran Pawar
  • Tim St. Hilaire
Oracle Application Express Finalists 
  • Morten Braten
  • Karen Cannell
  • Jari Laine
  • Paul MacMillan
  • Kiran Pawar
  • Trent Schafer
  • Juergen Schuster
Database Design Finalists
  • Heli Helskyaho
  • Mark Hoxey
  • Michelle Kolbe
  • Rob Lockard
The winners of the Oracle Database Developer Choice Awards will be announced at the YesSQL! Celebration on 27 October, during Oracle OpenWorld 2015.


  1. Good luck to all finalists.

  2. Steven,

    Can you explain the "down vote" phenomenon?

    Many of us had 0 points but 8 votes this morning (France time). Some think voters are voting finalists down but I wonder if it's not a technical issue in most cases.

    Strange to have a "down vote" option and to show a running tally.

    Anyway, off to "down vote" my nearest competitors - kidding!!!

    1. At start it was quite easy to find out who downvoted - i saw all voters list and in their accounts we can see for whom they upvoted(system adds points for upvotes), and the system doesn't show downvotes in account info.

  3. I don't know if I can explain it, Stew, except to say: I wish that it weren't possible to down vote. But we could not turn that off. I hope and fully expect that as the vote tallies accumulate, the relatively small number of down votes (caused perhaps by the most ardent supports of another finalist? Like our primary system, drawing out the most "extreme"(ly supportive) voters?) will be overwhelmed by the up votes.

  4. Thanks, Steven. Hope it's all a big success.

  5. Steven, quick question: Is it okay to ask family, friends and coworkers (who might not have OTN logins already) to vote for me? I had a quick look in the official rules, but got lost in the legalese... :-)

  6. Is it OK? Hmmm, well, first of all, if a member of your family or a friend or a co-worker is not a government employee, does live in Quebec or Italy, does not work for Oracle, was not an awards judge, they are eligible to vote. So no violation of the rule and it is OK from that regard.

    Is it OK to campaign for your award and ask your community, however you define it, to support you? Absolutely.

    Would it be wonderful if one person happened to be related distantly to Genghis Khan and therefore had "family" numbering in the millions ( and they all voted and thus this person won an award?

    Maybe not so wonderful.

    The objective of the awards program is to give to our Oracle Database Developer community, and to highlight the achievements of more of the leaders in that community.

    So far it is doing just that and we have overall high expectations for the impact of this awards program.

    Hope that helps.

    Congratulations, by the way, Morten, on your triple nomination!


Post a Comment

Popular posts from this blog

Get rid of mutating table trigger errors with the compound trigger

When something mutates, it is changing. Something that is changing is hard to analyze and to quantify. A mutating table error (ORA-04091) occurs when a row-level trigger tries to examine or change a table that is already undergoing change (via an INSERT, UPDATE, or DELETE statement). In particular, this error occurs when a row-level trigger attempts to read or write the table from which the trigger was fired. Fortunately, the same restriction does not apply in statement-level triggers. In this post, I demonstrate the kind of scenario that will result in an ORA-04091 errors. I then show the "traditional" solution, using a collection defined in a package. Then I demonstrate how to use the compound trigger, added in Oracle Database 11g Release1,  to solve the problem much more simply. All the code shown in this example may be found in this LiveSQL script . How to Get a Mutating Table Error I need to implement this rule on my employees table: Your new salary cannot be mo

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,

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p