You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2007/07/14 17:42:04 UTC
[jira] Commented: (DERBY-2935) DDMReader.readLengthAndCodePoint()
decodes long integer incorrectly
[ https://issues.apache.org/jira/browse/DERBY-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512720 ]
Bryan Pendleton commented on DERBY-2935:
----------------------------------------
Is it possible to write a new regression test, with some Long values which
require 6 and/or 8 bytes to encode, which demonstrates the bug and the fix?
> DDMReader.readLengthAndCodePoint() decodes long integer incorrectly
> -------------------------------------------------------------------
>
> Key: DERBY-2935
> URL: https://issues.apache.org/jira/browse/DERBY-2935
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.1, 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: decode-long.diff
>
>
> DDMReader.readLengthAndCodePoint() contains code to decode a long integer from a byte array. This code is broken since it uses int operations and not long operations in the decoding. The long might be encoded using four, six or eight bytes, and since Derby currently always uses the four bytes encoding, the bug is not exposed in the current code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.