Skip to main content

I love people who think logically - except when they expose my illogic

Received this via email today:
I have just found the PL/SQL Challenge and I am eager to get started. Under Instructions on the Quiz Introduction page is something to which I would like to call your attention. 
"For most quizzes, however, it is possible that more than one choice is correct, that all choices are correct, or that none of the choices are correct. You must check at least one box from those offered before you can submit your answer." 
How might one check a box and then submit if none of the choices are correct?
On first reading, I groaned. Really? Did I really leave a big hole like that in our quiz-taking process or - not quite as alarming - in my text? Is that a contradiction?

 No! No! No!

 There is an explanation which leaves me firmly on the right side of Logic.

 Can you see what it must be? 

 I will post this first as a small logic puzzle via Twitter, then I will update this post in a day or two with my answer.

 A day goes by.

 Another day goes by.

 Marcus solves the puzzle (see comments).

 Here's the answer:

 Nowhere in the text do I say that a "box" on the page must correlate to one of the choices. In fact, there is a box (a selection you can make) that is explicitly....
So that's the solution to the logic puzzle.

But Chris also makes a great point in the comments below that an explanation should not be needed for explanatory text. :-) So I am going to fix that text.

And that makes for a nice bonus to this post - I improve my application!

Comments

  1. MarcusOctober 6, 2016 at 1:57 AM

    There are checkboxes for the choices and one checkbox for "none is correct". Therefore not all boxes "from those offered" are connected to a choice.
    So if no choice is correct you can logically correct check the "none is correct" box.

    ReplyDelete
  2. NevenOctober 6, 2016 at 1:58 AM

    If all answer are wrong then you need to chek them all, question will be asked like chek all wrong etc. Simple play of word's. From PL/SQL side you have problem counting correct answers, in this case you need to do negation or even compare to null

    ReplyDelete
  3. Chris HuntOctober 6, 2016 at 2:53 AM

    Presumably, "boxes" doesn't necessarily mean the same thing as "choices." You might have a question offering choices A and B, and boxes for "A only", "B only", "A and B" and "Neither A nor B".

    However, whilst you may be convinced your wording is logical (whether or not my explanation is right) it fails on the grounds of clarity. We shouldn't need to solve a logic puzzle to understand what you mean.

    ReplyDelete
  4. Steven FeuersteinOctober 6, 2016 at 4:47 AM

    You got it, Marcus! Not all boxes are connected to a choice. As I will now update in my post, there is a selection for "No choice is correct."

    Chris, I am not sure if you looked at the quiz page, but I think it is entirely clear from the UI - however you raise a very good point. Our text should not be confusing in the least. I will fix that.

    ReplyDelete
  5. NevenOctober 6, 2016 at 6:40 AM

    I am not sure did i submit comment.... comment was what will happen if i answer one from four choice? what will be my % of correct answers?

    ReplyDelete
    Replies
    1. Steven FeuersteinOctober 6, 2016 at 7:11 AM

      If you check all boxes? Well, generally, our quizzes are NOT "all or nothing" (though some are). So you receive credit for the selections you made correctly, even if you also checked one or more boxes for incorrect choices.

      Delete
    2. NevenOctober 6, 2016 at 7:26 AM

      i know, that is why i am asking, lets say: we have 5 chk a,b,c,d and e ( e as all are wrong). i chek a and leave b,c,d,e empty, what will be my score 75% or 60% :)

      Delete
    3. Steven FeuersteinOctober 6, 2016 at 7:49 AM

      80%. You got four choices right, and 1 wrong. Assuming I understood you: 5 choices, all incorrect, choose one as correct.

      Delete
    4. NevenOctober 6, 2016 at 7:59 AM

      ah let me try again regroup my thought
      a) answer1
      b) answer2
      c) answer3
      d) answer4
      e)all wrong
      ( lets say e is correct)
      i mark only a(answer) as correct
      in this case what is % of correct answers?

      Delete
    5. Steven FeuersteinOctober 6, 2016 at 8:10 AM

      You get 75% correct. "All wrong" or "No choice is correct" is not a "choice" that is counted in the scoring. It is merely a quick and easy way to let the player turn off all choices.

      Delete
  6. Steven FeuersteinOctober 6, 2016 at 7:48 AM

    This comment has been removed by the author.

    ReplyDelete
  7. UnknownOctober 6, 2016 at 11:28 AM

    The piece that states "...or none of the answer choices is correct" contradicts the answer choice "no choice is correct" because that last choice is correct. Unless that last box is not a choice

    ReplyDelete
    Replies
    1. Steven FeuersteinOctober 6, 2016 at 12:06 PM

      That's right it is NOT a choice. It is a "meta-choice" that disables all checked choices.

      Delete

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