[ http://issues.apache.org/jira/browse/DERBY-1516?page=all ]
Craig Russell updated DERBY-1516:
---------------------------------
Attachment: DERBY-1516.patch
This patch incorporates all of the comments (thank you, Kathey and Dag) and
therefore the logic is simpler for detecting invalid positions.
The canons for blobclob4BLOB have been changed to reflect that a request for
bytes or a substring starting at position (length + 1) is now valid and the
result will be of zero length, regardless of the length requested. This will
not break existing applications except possibly regression testing applications
that depend on Derby throwing an exception for this case.
> Inconsistent behavior for getBytes and getSubString for embedded versus
> network
> -------------------------------------------------------------------------------
>
> Key: DERBY-1516
> URL: http://issues.apache.org/jira/browse/DERBY-1516
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Craig Russell
> Assigned To: Craig Russell
> Priority: Minor
> Attachments: DERBY-1516.patch, DERBY-1516.patch, DERBY-1516.patch,
> DERBY-1516.patch, DERBY-1516.patch
>
>
> org.apache.derby.client.am.Clob.getSubString(pos, length) and
> org.apache.derby.client.am.Blob.getBytes(pos, length) check the length for
> less than zero.
> if ((pos <= 0) || (length < 0)) {
> throw new SqlException(agent_.logWriter_, "Invalid position "
> + pos + " or length " + length);
> But org.apache.derby.impl.jdbc.EmbedClob(pos, length) and
> org.apache.derby.impl.jdbc.EmbedBlob(pos, length) check the length for less
> than or equal to zero.
> if (length <= 0)
> throw Util.generateCsSQLException(
> SQLState.BLOB_NONPOSITIVE_LENGTH, new Integer(length));
> The specification does not disallow length of zero, so zero length should be
> allowed. I believe that the implementation in org.apache.derby.client.am is
> correct, and the implementation in org.apache.derby.impl.jdbc is incorrect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
