Note that there are some explanatory texts on larger screens.

plurals
  1. POExceptions into clause does not work when creating a constraint
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CObash Oracle threads are apparently a quick way to get points...how is this +2 with not a single comment? The error you get is telling you the primary key fields cannot contain nulls. It doesn't mean Oracle exceptions don't work. Look at your table, do you see any contraints?
      singulars
    2. CO@tbone, this isn't about exception handling. This is about the "exceptions into" clause. What the OP is describing is exactly the case, and is a legitimate question as the documentation does not tell you this information. The problem is you can't create the constraint AND report exceptions in one step. How is this "bashing" Oracle?
      singulars
    3. CO@DCookie I understand its about the "exceptions into" clause, but the title is "oracle exceptions do not work". Its not an Oracle issue (how can the constraint log exceptions when it cannot even be created, you must either create it first before loading nulls or do as you suggest as create it disabled). Once created, it can do its job. I just find it funny that I ran into several "why does Oracle suck" threads that immediately gain points based on, well, I don't know. For example,see http://stackoverflow.com/questions/11191299/why-is-there-a-maximum-length-for-stored-procedure-names.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload