Jul 25 2009
ORA-00001: unique constraint (METALINK.SYS_C005417) violated

This is a partial screenshot of an application without a decent error handling.
Do you recognize it?
It goes without saying that no further comments are needed…
Jul 25 2009

This is a partial screenshot of an application without a decent error handling.
Do you recognize it?
It goes without saying that no further comments are needed…
All comments are filtered by Akismet and then moderated by me. So, it should be no surprise that spam and anything wholly inappropriate has no chance of making it onto the site. To send questions or comments not related to this blog post please use the contact form.
July 26th, 2009 at 2:55 am
Forget the application, they should be giving their unique constraints some sort of reasonable name.
July 26th, 2009 at 9:25 am
Hi Gary
I fully agree with you about the name of unique constraints. But, IMHO, the name of the constraints is much less important than the error handling…
Cheers,
Chris
July 30th, 2009 at 11:21 am
Grin … maybe they are having trouble FINDING the code produing the error – if the developers are not allowed access
to prodcution environment definitions, it can be rather tedious to find a constraint with quite another
name in test & dev environments. I HATE unnamed constraints …..