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
Labels:

Comments

Post a Comment

Popular posts from this blog

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

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged 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 latter part...
31 comments
Read more