Skip to main content

Oracle Dev Gym PL/SQL Championship for 2019 Players

Throughout 2019, over 1200 Oracle Database developers participated in the Oracle Dev Gym PL/SQL Challenge weekly tournament. The top 50 ranked players shown below will compete for top honors in a championship on February 18, 2020.

The number in parentheses after their names are the number of championships in which they have already participated. As you can see, there are some very dedicated players here!

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

Name Rank
Stelios Vlasopoulos (16) 1
mentzel.iudith (19) 2
NielsHecker (20) 3
Chad Lee (16) 4
Peterman (6) 5
siimkask (19) 6
_tiki_4_ (12) 7
Chase Mei (5) 8
Ludovic Szewczyk (4) 9
li_bao (7) 10
MarkusId (0) 11
Andrey Zaytsev (8) 12
Michal P. (3) 13
Arjun Barath (0) 14
Ivan Blanarik (13) 15
Maxim Borunov (6) 16
lmikhailov (0) 17
mcelaya (4) 18
tonyC (5) 19
patch72 (6) 20
Karel_Prech (9) 21
Sandra99 (3) 22
Oleksiy Ponomarenko (4) 23
Mike Tessier (3) 24
Vyacheslav Stepanov (18) 25
Jan Šerák (5) 26
seanm95 (6) 27
msonkoly (4) 28
Rakesh Dadhich (11) 29
pjas (2) 30
PZOL (5) 31
korolkov_d_a (0) 32
Henry_A (6) 33
Talebian (6) 34
Sartograph (2) 35
Rytis Budreika (7) 36
syukhno (2) 37
NickL (4) 38
swesley_perth (5) 39
Nikolay Loginov (0) 40
Sachi (3) 41
craig.mcfarlane (0) 42
RalfK (1) 43
JeroenR (12) 44
umir (0) 45
JasonC (4) 46
Otto Palenicek (3) 47
Aleksei Davletiarov (1) 48
ted (2) 49
StasKa (0) 50

Comments

Popular posts from this blog

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...

Three tips for getting started right with Oracle Database development

By "Oracle Database development", I mean, more or less, writing SQL and PL/SQL. I assume in this post that you have access to Oracle Database (which you can get via Cloud services, Docker , GitHub and OTN ). A. Use a powerful IDE, designed with database programming in mind. There are lots of editors out there, and many IDEs that work with Oracle Database. Sure, you could use Notepad, but OMG the productivity loss. You could also use a popular editor like Sublime, and then it get it working with Oracle. I suggest, however, that you  download  and install Oracle's own own, free, powerful IDE: SQL Developer . If you like to complement your graphical IDE with a command line tool (or OMG if you actually prefer  a command line tool to a graphical interface), you should also check out the relatively new and generating-lots-of-excitement SQLcl . B. Enable compile-time warnings and PL/Scope. The database has tons of useful functionality burned right into it, ready for...

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...