[
https://issues.apache.org/jira/browse/DERBY-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512873
]
Knut Anders Hatlen commented on DERBY-2935:
-------------------------------------------
I don't think it's possible to test the fix with a JDBC test, at least, since
Derby doesn't support data types with length >= 2^31, but it might be possible
to force 6 and 8 byte values in derbynet/testProtocol.java. I'll see if I can
come up with something.
> 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.
