[jira] [Commented] (DERBY-6803) Change Sqlca and SqlException in NetworkClient to call MessageUtils

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660030#comment-14660030 ] 

ASF subversion and git services commented on DERBY-6803:
--------------------------------------------------------

Commit 1694492 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1694492 ]

DERBY-6803: Change Sqlca and SqlException to call MessageUtils

This patch was contributed by Abhinav Gupta (abhinavgupta2004 at gmail dot com)

This patch modifies the code in the client libraries
which analyzes the error or exception information in
the sqlerrmc message data, to use the new features of
the MessageUtils shared code to decode the message format.

In particular, the code can now locate and decode the
arguments as well as the message id, and therefore can
include those arguments when constructing a custom
Derby-specific subclass of SQLIntegrityConstraintViolationException.

> Change Sqlca and SqlException in NetworkClient to call MessageUtils
> -------------------------------------------------------------------
>
>                 Key: DERBY-6803
>                 URL: https://issues.apache.org/jira/browse/DERBY-6803
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC, Network Client, Network Server
>            Reporter: Bryan Pendleton
>            Assignee: Abhinav Gupta
>            Priority: Minor
>         Attachments: MessageUtils_1.diff, MessageUtils_2.diff, clientChanges.diff, clientOutline.diff
>
>
> Currently, the network client code is not able to access the arguments
> that are associated with a Derby exception that is returned by the engine.
> We would like to change the network client code, specifically the code
> in the Sqlca and SqlException classes, so that it uses the new MessageUtils
> class to access the exception arguments.
> We wish to take the exception arguments and associate them with the
> SqlException object, so that when the client calls the SQLExceptionFactory
> to create a SQLException to throw to the user application, it can create
> a Derby-specific subclass of that exception, when appropriate, which
> contains the arguments that the server sent to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)