[ 
https://issues.apache.org/jira/browse/OFBIZ-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892100#action_12892100
 ] 

Jacques Le Roux commented on OFBIZ-3870:
----------------------------------------

Hi Deyan,

[In this thread|http://tinyurl.com/2bhvczn] Adrian suggested to handle the 2 
specs using the an attribute of the datasource element of entitytengine.xml. I 
don't find any entitytengine.xml in your patch. Did you handle it another way 
(I did not look into details)

> Extend GenericEntityExceptions and provide subclasses for different types of 
> database errors
> --------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-3870
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3870
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Deyan
>            Assignee: Adam Heath
>         Attachments: GenericEntityException_SQLState.patch
>
>
> Currently EntityEngine provides only GenericDuplicateKeyException which is 
> never used. 
> It is needed for development purposes to create more detailed exceptions 
> level which allows developers to better handle 
> database errors and warnings and help distinguish between recoverable and 
> not-recoverable errors. 
> This improvement provides the following classes: 
> GenericIntegrityConstraintViolationException -> GenericEntityException
> GenericRestrictViolationException -> 
> GenericIntegrityConstraintViolationException
> GenericNotNullViolationException -> 
> GenericIntegrityConstraintViolationException
> GenericGoreignKeyViolationException -> 
> GenericIntegrityConstraintViolationException
> GenericDuplicateKeyException -> GenericIntegrityConstraintViolationException 
> ( modified superclass )
> GEnericCheckViolationException -> GenericIntegrityConstraintViolationException

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to