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


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 ErrorI need to implement this rule on my employees table:
Your new salary cannot be more than 25x th…

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, reducing context switchi…

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…