[
https://issues.apache.org/jira/browse/DERBY-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4738:
--------------------------------------
Attachment: init_length.diff
The attached follow-up patch (init_length.diff) removes the initialization of
the length variable to 0 from the top of the method, and moves the declaration
of the variable down to the point where it's set to its real value. This will
make the compiler complain if someone tries to use the length variable before
it has been properly initialized.
Committed revision 961903.
> correct error prompt for nonpositive length in Blob.setBytesX()
> ---------------------------------------------------------------
>
> Key: DERBY-4738
> URL: https://issues.apache.org/jira/browse/DERBY-4738
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.7.0.0
> Reporter: Yun Lee
> Assignee: Yun Lee
> Fix For: 10.7.0.0
>
> Attachments: derby-4738.patch, derby-4738.stat, init_length.diff
>
>
> In Blob.setBytesX(), when a nonpositive length value (len) is passed in, a
> SqlException with ClientMessageId of SQLState.BLOB_NONPOSITIVE_LENGTH is
> created, however, it uses length, a wrong length value, which is still zero
> here.
> if ( len < 0 ) {
> throw new SqlException(agent_.logWriter_,
> new ClientMessageId(SQLState.BLOB_NONPOSITIVE_LENGTH),
> new Integer(length));
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
