>Hi,
>
>I am looking for input on how your UI layer handles messages of failure to update database because of constraint violation. For example, if a user enters a value in a FK column that has not match in UNIQUE field of primary table, this will cause the update to return an error. The error message is very long and very technical in nature. Do you show the entire message to your users and hope they understand? Or what other approaches you use?
>
>TIA for any input.

Generally I log the error details if possible for developer reference and present the user the 'short' version of an error. "The application has encountered a " + some simple wording of the error type + "error and has to close/reload/burn the server to the ground/whatever".

Give a user a nice convoluted error message and they generally get overexcited.