Skip to main content

Fifty top PL/SQL players heading to the Dev Gym Championship!


2017 is no more. Which means that there are no more quizzes to be taken in 2017. Which means that we can now compute the rankings for the weekly PL/SQL tournament at the Dev Gym - and get ready for the 2017 championship event!

The top fifty-ranked players from 2017 will be invited to participate in the PL/SQL Challenge Championship for 2017, which will take place in March 2018 (date still to be finalized).

The number in parentheses after their names are the number of championships in which they have already participated. As you can see, many of these players are incredibly dedicated to their craft as Oracle Database Developers generally and to their standing on the Dev Gym in particular.

Congratulations to all listed below on their accomplishment and best of luck in the upcoming competition!

By the way, if you are not yet taking our weekly tournament quizzes at the Dev Gym, give it a try. You do not have to play competitively; you can opt-out of rankings.  Heck, you can even play incognito by changing your gym name. The main thing is:

Expertise Through Exercise!


Name Rank Qualification Country
Stelios Vlasopoulos (14) 1 Top 50 No Country Set
mentzel.iudith (17) 2 Top 50 Israel
NielsHecker (18) 3 Top 50 Germany
James Su (12) 4 Top 50 Canada
siimkask (17) 5 Top 50 Estonia
Andrey Zaytsev (6) 6 Top 50 Russia
Chad Lee (14) 7 Top 50 United States
Tony Winn (6) 8 Top 50 Australia
Karel_Prech (7) 9 Top 50 No Country Set
Jan Šerák (3) 10 Top 50 Czech Republic
li_bao (5) 11 Top 50 Russia
Ludovic Szewczyk (2) 12 Top 50 No Country Set
JustinCave (14) 13 Top 50 United States
_tiki_4_ (10) 14 Top 50 Germany
HSteijntjes (0) 15 Top 50 Netherlands
patch72 (4) 16 Top 50 Netherlands
Vyacheslav Stepanov (16) 17 Top 50 No Country Set
tonyC (3) 18 Top 50 United Kingdom
seanm95 (4) 19 Top 50 United States
Mike Tessier (1) 20 Top 50 Canada
Henry_A (4) 21 Top 50 Czech Republic
Alexey Ponomarenko (2) 22 Top 50 No Country Set
Michal P. (1) 23 Top 50 Poland
Chase Mei (3) 24 Top 50 Canada
swesley_perth (3) 25 Top 50 Australia
mcelaya (2) 26 Top 50 Spain
Sandra99 (1) 27 Top 50 Italy
Sartograph (0) 28 Top 50 Germany
Maxim Borunov (4) 29 Top 50 Russia
JasonC (2) 30 Top 50 United Kingdom
coba (2) 31 Top 50 No Country Set
msonkoly (2) 32 Top 50 Hungary
berkeso (1) 33 Top 50 Hungary
Rakesh Dadhich (9) 34 Top 50 India
Talebian (4) 35 Top 50 Netherlands
USER35250 (0) 36 Top 50 No Country Set
Rytis Budreika (5) 37 Top 50 Lithuania
pablomatico (0) 38 Top 50 No Country Set
Hertha Rettinger (0) 39 Top 50 Germany
Kias (0) 40 Top 50 No Country Set
Otto Palenicek (1) 41 Top 50 Germany
Rimantas Adomauskas (4) 42 Top 50 Lithuania
USER59562 (0) 43 Top 50 No Country Set
PZOL (3) 44 Top 50 Hungary
Enrico Rebecchi (1) 45 Top 50 Italy
ivan_blanarik (11) 46 Top 50 Slovakia
whab@tele2.at (0) 47 Top 50 Austria
VictorD (4) 48 Top 50 Russia
NickL (2) 49 Top 50 United Kingdom
Joaquin_Gonzalez (11) 50 Top 50 Spain

Comments

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 more than 25x th…

Table Functions, Part 1: Introduction and Exploration

August 2018 update: please do feel encourage to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done!


Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs.

So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into.

Of course, I am not the first to do so. I encourage to check out the documentation, as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall. Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latte…

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