Skip to main content

Time for another Dev Gym PL/SQL Championship!

A new year has arrived, and that means that it's time (or will soon be time) for the PL/SQL Challenge Championship, when up to fifty top players from last year's PL/SQL tournament quizzes compete for top honors.

The following players will be invited to participate in the PL/SQL Challenge Championship for 2018, currently scheduled to take place on 21 March (hey, it takes some time to put together five advanced quizzes without any mistakes in them!).

The number in parentheses after their names are the number of championships in which they have already participated (note: from 2010 through 2013, we held quarterly championships for our then daily PL/SQL quiz!).

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


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

Comments

Popular posts from this blog

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

The future of Oracle PL/SQL: some thoughts on Sten Vesterli's thoughts

Sten Vesterli published a very thought-provoking post on his blog: Please stop reading this post, and read that one. When you are done, come on back here for my thoughts on Sten's thoughts. OK. You read it. Here we go. First, thanks, Sten, for being such an interesting, wise, sometimes provocative voice in our community. Next, Sten writes: Now, on the one hand, I certainly agree that the vast majority of young developers are currently caught up in the modern version of a Gold Rush, which is: "Build an app using JavaScript, pay no attention to that database behind the curtain." But I can assure you that I still do meet young PL/SQL programmers, regularly, when I am at conferences and doing onsite presentations at companies. So, young person who writes PL/SQL: do not be afraid! You are not alone! And you are super-smart to have made the choice you did. :-) Next, Sten offers this advice to managers: I agree that PL/SQL is a "spec...