Skip to main content

PL/SQL Puzzle: Getting the "right" error message to appear

I posted the following puzzle on Twitter:
What change(s) can you make to this code so that "ORA-00001: unique constraint" appears on the screen after execution?
Try it yourself before reading the rest of the post!


White space


so you do not immediately



see my answer. 



:-)


Here are the answers from the TwitterSphere:

Change line 5's assignment to dbms_sql.number_table(1=>1,2=>1)

In other words, try to insert the same value twice. Since there is a unique index on the column, that will cause ORA-00001 to be raised.

So that will do it, right?

Wrong. Hans and Dirk both point out why that is not enough, and offer the second part of the solution:

The value deposited in the error_code field of the SQL%BULK_EXCEPTIONS array is unsigned. In other words, 1 rather than -1 is stored. Unfortunately, the SQLERRM function assumes that the error code you pass it will be signed (negatively). So you must multiply the value in the pseudo-collection by -1. Then SQLERRM will return the right string.

Or as Dirk puts it:

(sqlerrm (sql%bulk_exceptions (indx).error_code));

must be

(sqlerrm (0 - sql%bulk_exceptions (indx).error_code));

You don't really need the 0, though. You can write simply:

(sqlerrm (-sql%bulk_exceptions (indx).error_code));

You can see all these variations at work in my LiveSQL script.

Actually, I was surprised that I did not receive any "silly" answers. After all, there are lots of ways to get "ORA-00001: unique constraint" to appear on the screen, such as:

DECLARE 
   two_ts DBMS_SQL.number_table := DBMS_SQL.number_table (1=>1,2=>2); 
BEGIN 
   DBMS_OUTPUT.PUT_LINE ('ORA-00001: unique constraint');
   RETURN;
   
   FORALL indx IN 1 .. 2 
   SAVE EXCEPTIONS 
      INSERT INTO t VALUES (two_ts(indx)); 
   DBMS_OUTPUT.put_line (SQL%ROWCOUNT || ' inserted'); 
   ROLLBACK; 
EXCEPTION 
   WHEN others 
   THEN 
      FOR indx IN 1 .. SQL%BULK_EXCEPTIONS.COUNT 
      LOOP 
         DBMS_OUTPUT.put_line 
            (SQLERRM (SQL%BULK_EXCEPTIONS (indx).ERROR_CODE)); 
      END LOOP; 
END; 

Yes, that's right, simply display it on the screen and then shortcut everything else with RETURN; (or not, let the rest of the code execute unchanged).

I guess it was a serious week for the Oracle Database developer community. :-)

Comments

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

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get

My two favorite APEX 5 features: Regional Display Selector and Cards

We (the over-sized development team for the PL/SQL Challenge - myself and my son, Eli) have been busy creating a new website on top of the PLCH platform (tables and packages): The Oracle Dev Gym! In a few short months (and just a part time involvement by yours truly), we have leveraged Oracle Application Express 5 to create what I think is an elegant, easy-to-use site that our users will absolutely love.  We plan to initially make the Dev Gym available only for current users of PL/SQL Challenge, so we can get feedback from our loyal user base. We will make the necessary adjustments and then offer it for general availability later this year. Anyway, more on that as the date approaches (the date being June 27, the APEX Open Mic Night at Kscope16 , where I will present it to a packed room of APEX experts). What I want to talk about today are two features of APEX that are making me so happy these days: Regional Display Selector and Cards. Regional Display Sel