Skip to main content

Help me test a new Oracle Dev Gym feature: Classes

Back in June, we opened the "early adaptor" doors to the Oracle Dev Gym, a modern, mobile website on top of the PL/SQL Challenge's quiz platform.



We've gotten lots of great feedback and continue to develop the site (with plans to make it generally available in Q1 CY2017).

The next feature we will be releasing on the Dev Gym is Classes.

Classes will offer us multiple opportunities to present workouts and quizzes to users.

For example, on Friday 26 August, I will hold a "live" Dev Gym workout at a Chicago Oracle Group event. We will do this via a Class. Other classes in the future will be tied to monthly webcasts and more.

And now my request for help: I'd much rather expose and fix any bugs a week before the event, rather than at the event itself. :-)

So I have set up a test class for everyone starting at 18 August 15:00 UTC (10 AM US Central time). 

I'd like as many of you as possible to take the quizzes in the two hours that the class will be open - and if at all possible, start the workout promptly at 15:00.

It consists simply of three quizzes, so it won't take you long to do.

To take a class, simply click on the Classes link in the left side navigation bar:


Then click on the name of the class you want to take (there will only be one on Thursday):


Finally, click on the Join Class button and you will be added as a student for the class. You can do this anytime before and during the class. If you have turned on reminders for quizzes, you will also receive email reminders for this class.


If you join the class after it's started, you will be taken right to the class workout.

We are working hard to keep this site simple and intuitive, so I hope that you will be able to navigate through the class without any difficulty. 

If you do run into any sorts of problems, or have ideas for how we can improve Dev Gym Classes, just click on Feedback on the top right corner of the page:


Thanks in advance for your help!

Oh and if you have not yet taken quizzes at the PL/SQL Challenge or Dev Gym, now would be a great time to get started! 

Once you are signed in to your Oracle Account, you'll be ready to go.

Comments

Popular posts from this blog

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...

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, ...

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...