New Ranking Tags Feature of Oracle Dev Gym

You can take quizzes, workouts and classes at the Oracle Dev Gym solely with the objective of learning and improving your expertise in Oracle technologies.

You can also play competitively, which means that you will be ranked when you take a tournament quiz. You can see all the rankings for tournaments by clicking on the Leaderboard tab.

But what if you'd like to see how you ranked compared to your co-workers or friends?

What if your entire dev team wants to take a workout together and then compare how you all did?

I have one answer to those questions: ranking tags!

Click on your name in upper right, select Profile Settings.

Click on the Ranking Tags tab.

It's empty! OK, now it's time to talk to your friends or co-workers. Decide on a tag that you can use to identify your little circle. Aim for something obviously unique. These are "just" tags, so if you use something like "ORADEV" and so does someone else, you will be in the same ranking filter list.

So decide on a tag, invite your friends to do the same thing. You can see everyone with the same tag in the profile settings page.

Once you've done that, you can choose the tag both on Leaderboard ranking reports and on a new Workout Rankings modal. You will see a button to open this modal when (a) you've completed the workout and (b) you've added at least one ranking tag to your profile.

The two minute video above shows you all of this. Enjoy!

Comments

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

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,

Working With JSON Arrays in PL/SQL

Oracle Database 12c Release 2 built upon the 12.1 SQL/JSON features by adding a number of builtin object types (similar to classes in object-oriented languages) for manipulating JSON data in PL/SQL blocks. In this post, I explore some of the array-oriented JSON features, all made available through the JSON_ARRAY_T type and its methods. Just like a class, an object type offers a pre-defined constructor function to instantiate new instances of that type, static methods and member methods. Here are the methods you are most likely to use: A couple of things to remember, generally, about working with JSON elements generally and JSON arrays specifically in PL/SQL: Error Handling Behavior By default, if an error occurs when you call a member method for your JSON array (or object), NULL is returned. In other words, an exception is not raised back to your block. If you want errors to be propagated from the method as an exception, call the ON_ERROR method and pass a value greate

Obsessed with Oracle PL/SQL

Search This Blog