Skip to main content

Logic Reigns in the Oracle Dev Gym Logic Championship

Logic is at the very heart of programming, so we complement our quizzes on SQL, PL/SQL and so on with a weekly Logic tournament. And then at the end of the year, the top 50 ranked players qualify for our annual championship.

The following players will be invited to participate in the Logic Annual Championship for 2018, currently scheduled to take place on 19 February.

The number in parentheses after their names are the number of championships in which they have already participated.

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

Name Rank
Stelios Vlasopoulos (5) 1
Pavel Zeman (4) 2
mentzel.iudith (5) 3
Ludovic Szewczyk (1) 4
James Su (5) 5
Chad Lee (5) 6
Tony Winn (3) 7
Rytis Budreika (5) 8
ted (5) 9
Kanellos (4) 10
Cor van Berkel (4) 11
Köteles Zsolt (4) 12
Vijay Mahawar (5) 13
RalfK (4) 14
pjas (1) 15
Mike Tessier (3) 16
seanm95 (5) 17
NickL (4) 18
Michal P. (1) 19
Eric Levin (4) 20
Sandra99 (5) 21
Mehrab (5) 22
JasonC (5) 23
Talebian (4) 24
NielsHecker (5) 25
richdellheim (5) 26
Sartograph (3) 27
tonyC (4) 28
Kias (2) 29
craig.mcfarlane (4) 30
umir (5) 31
li_bao (3) 32
Vyacheslav Stepanov (5) 33
Stanislovas (2) 34
msonkoly (3) 35
Patel Sanjay (1) 36
mcelaya (3) 37
whab@tele2.at (3) 38
MarkusId (0) 39
saddaymay (2) 40
gabt (0) 41
Alexuboo (1) 42
Vladimir13 (3) 43
JustinCave (5) 44
TZ (3) 45
Stephan (0) 46
Dan Kiser (4) 47
jamesravid (0) 48
Arūnas Antanaitis (3) 49
Henry_A (1) 50
Labels:

Comments

Post a Comment

Popular posts from this blog

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 p...
24 comments
Read more

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...
8 comments
Read more

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