Skip to main content

Rankings for Logic Annual Championship for 2019

You will find below the rankings for the Logic Annual Championship for 2019, held in February 2020 on the Oracle Dev Gym. The number next to the player's name is the number of times that player has participated in a championship. Below the table of results for this championship, you will find another list showing the championship history of each of these players.

Congratulations first and foremost to our top-ranked players:

1st Place: Stelios Vlasopoulos

2nd Place: Sartograph

3rd Place: NielsHecker

Next, congratulations to everyone who played in the championship. We hope you found it entertaining, challenging and educational. And for those who were not able to participate in the championship, you can take the quizzes through the Practice feature. We will also make the championship as a whole available as a Workout, so you can take it just like these players did.

Finally, many thanks to Eli Feuerstein, Logic Quizmaster who provided a very challenging set of quizzes, and our deepest gratitude to our reviewers, especially Livio Curzola, who has once again performed an invaluable service to our community.

Rank Name Total Time % Correct Total Score
1 Stelios Vlasopoulos (7) 10 m 100% 4449
2 Sartograph (5) 10 m 100% 4446
3 NielsHecker (7) 12 m 100% 4436
4 Ankitg97 (1) 23 m 100% 4381
5 Talebian (6) 25 m 100% 4370
6 Pavel Zeman (6) 36 m 100% 4320
7 Michal P. (3) 39 m 100% 4303
8 whab@tele2.at (5) 44 m 100% 4280
9 Tarush Shenoy (1) 49 m 100% 4253
10 Mike Tessier (5) 54 m 100% 4230
11 Eric Levin (6) 57 m 100% 4212
12 mcelaya (5) 57 m 100% 4211
13 Sayyad Hussen (1) 57 m 100% 4210
14 SQLMonster (1) 58 m 100% 4209
15 Tony Winn (5) 58 m 100% 4208
16 MarkusId (2) 28 m 96% 4168
17 Chad Lee (7) 40 m 96% 4110
18 mentzel.iudith (7) 42 m 96% 4099
19 Sandra99 (7) 58 m 96% 4022
20 li_bao (5) 30 m 92% 3974
21 Rytis Budreika (7) 56 m 92% 3842
22 gabt (2) 58 m 92% 3834
23 JasonC (7) 34 m 88% 3767
24 ted (7) 41 m 88% 3729
25 Dan Kiser (6) 56 m 79% 3281
26 lmikhailov (1) 56 m 79% 3280
27 craig.mcfarlane (6) 59 m 79% 3263
28 Stanislovas (4) 54 m 75% 3103
29 richdellheim (7) 58 m 75% 3085
30 JohnTay1or (1) 52 m 71% 2924
31 Ludovic Szewczyk (3) 58 m 71% 2898
32 seanm95 (7) 55 m 67% 2722
33 Vijay Mahawar (7) 55 m 67% 2721
34 Cor van Berkel (6) 56 m 67% 2719
35 NickL (6) 58 m 67% 2706
36 msonkoly (5) 59 m 67% 2703
37 ijaveed (1) 25 m 50% 2121
38 Henry_A (3) 04 m 46% 2040

Championship Performance History

After each name, the quarter in which he or she played, and the ranking in that championship.

Name History
Stelios Vlasopoulos 2013:16th, 2014:29th, 2015:19th, 2016:8th, 2017:1st, 2018:1st, 2019:1st
Sartograph 2015:24th, 2016:21st, 2017:5th, 2018:3rd, 2019:2nd
NielsHecker 2013:3rd, 2014:21st, 2015:11th, 2016:27th, 2017:19th, 2018:13th, 2019:3rd
Ankitg97 2019:4th
Talebian 2014:10th, 2015:9th, 2018:14th, 2019:5th
Pavel Zeman 2014:7th, 2015:1st, 2016:3rd, 2017:2nd, 2018:2nd, 2019:6th
Michal P. 2017:24th, 2018:23rd, 2019:7th
whab@tele2.at 2015:30th, 2017:33rd, 2018:18th, 2019:8th
Tarush Shenoy 2019:9th
Mike Tessier 2015:40th, 2016:20th, 2017:4th, 2018:19th, 2019:10th
Eric Levin 2014:22nd, 2015:36th, 2016:28th, 2017:18th, 2019:11th
mcelaya 2015:25th, 2017:32nd, 2018:29th, 2019:12th
Sayyad Hussen 2019:13th
SQLMonster 2019:14th
Tony Winn 2013:25th, 2016:25th, 2017:7th, 2018:16th, 2019:15th
MarkusId 2019:16th
Chad Lee 2013:34th, 2014:31st, 2015:38th, 2016:5th, 2017:8th, 2018:20th, 2019:17th
mentzel.iudith 2013:4th, 2014:18th, 2015:22nd, 2016:6th, 2017:6th, 2018:11th, 2019:18th
Sandra99 2013:17th, 2014:19th, 2015:7th, 2016:4th, 2017:10th, 2018:4th, 2019:19th
li_bao 2015:39th, 2019:20th
Rytis Budreika 2013:12th, 2014:3rd, 2015:28th, 2017:29th, 2019:21st
gabt 2018:15th, 2019:22nd
JasonC 2013:35th, 2014:12th, 2015:26th, 2016:2nd, 2017:9th, 2018:22nd, 2019:23rd
ted 2013:27th, 2015:6th, 2017:14th, 2019:24th
Dan Kiser 2016:22nd, 2017:35th, 2019:25th
lmikhailov 2019:26th
craig.mcfarlane 2014:8th, 2015:5th, 2017:16th, 2018:12th, 2019:27th
Stanislovas 2016:31st, 2017:26th, 2018:24th, 2019:28th
richdellheim 2013:31st, 2014:6th, 2015:8th, 2016:13th, 2017:31st, 2018:10th, 2019:29th
JohnTay1or 2019:30th
Ludovic Szewczyk 2018:26th, 2019:31st
seanm95 2013:24th, 2014:26th, 2015:33rd, 2016:12th, 2017:22nd, 2018:5th, 2019:32nd
Vijay Mahawar 2015:27th, 2016:24th, 2017:17th, 2018:17th, 2019:33rd
Cor van Berkel 2014:36th, 2015:17th, 2018:27th, 2019:34th
NickL 2014:14th, 2015:23rd, 2017:20th, 2018:7th, 2019:35th
msonkoly 2015:21st, 2017:23rd, 2018:21st, 2019:36th
ijaveed 2019:37th
Henry_A 2014:35th, 2019:38th
Labels:

Comments

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
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

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more