CreateException: error message for unique constraint isn't very helpful

Question

When I create a CMP bean in a table containing a unique constraint, I receive the expected CreateException. However, the error message looks like:
"Error creating EntityBean: ORA-00001: unique constraint (SID.SYS_C005934) violated"
This message isn't particularly helpful, especially if there are, say, three unique constraints, and the only difference is the "SYS_CXXXXXX" number. There is no way to tell which number applies to which constraint, and this makes it difficult to give a "readable" error message to the end-user.
Is there a way of either (a) Setting the error message to be thrown by a unique constraint violation or (b) A means of getting the column name that was the focus of the violation? Either of these would make it easier to map an "readable" error message to the exception.
Much thanks,
-Roger

Answer 1

Hi Roger,
How about trying to give meaningfull names while creating the table, so that when the exception is throw, it would be easy to find the column
which generated the exception.
something like,
SQL>create table table1
id number(10) constraint UNIQUE_TABLE1_ID unique
Table created
SQL> insert into table1 values(1);
1 row created.
SQL> insert into table1 values(1);
insert into table1 values(1)
ERROR at line 1:
ORA-00001: unique constraint (SCOTT.UNIQUE_TABLE1_ID) violated
Hope this helps
Regards
Elango.