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

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…