[jira] Updated: (DERBY-3977) Clob.truncate with a value greater than the Clob length raises different exceptions in embedded and client driver

["Kristian Waagan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-3977:
-----------------------------------

    Attachment: derby-3977-1a-change_emb_exception.diff

Patch 1a changes the exception thrown in the embedded driver from XJ076 to XJ079. It now matches the client driver.
I ran derbyall and suites.All, and got no failures due to the change of exception (except for the two new tests, which I have modified in the patch).

Patch ready for review.

> Clob.truncate with a value greater than the Clob length raises different exceptions in embedded and client driver
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3977
>                 URL: https://issues.apache.org/jira/browse/DERBY-3977
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.3.3.0, 10.4.2.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-3977-1a-change_emb_exception.diff
>
>
> Calling Clob.truncate with a value that is greater then the Clob length raises different SQLExceptions in the client and the embedded driver.
>  o Client: SQLState.BLOB_LENGTH_TOO_LONG - XJ079
>  o Embedded: SQLState.BLOB_POSITION_TOO_LARGE - XJ076
> I believe the fix is simple enough  - change one of the exceptions.
> Which one most closely describes the situation?
> A release note is needed for this fix.
> Also note the following from the Java API docs:
> "void truncate(long len)
>               throws SQLException
>     Truncates the CLOB value that this Clob designates to have a length of len characters.
>     Note: If the value specified for pos is greater then the length+1 of the CLOB value then the behavior is undefined. Some JDBC drivers may throw a SQLException while other drivers may support this operation.
> "
> This opens for a change of behavior as well.
> There seems to an inconsistency in the docs, possibly due to rephrasing - it references both len and pos. The latter isn't used anywhere else in the JavaDoc for truncate.
> And what should the result of truncate(length+1) be?

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