[DERBY-5536] Client's ResultSet#getLong does not range check when converting from a DECIMAL column - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 10.9.1.0
Component/s: JDBC, Network Client
Labels:
- derby_backport_reject_10_8

Bug behavior facts:

Deviation from standard, Embedded/Client difference, Wrong query result

Description

Derby's DECIMAL can contain an integer of 31 digits. This can overflow a long. The embedded JDBC driver catches this, but the client does not and can yield a corrupt long, cf enclosed repro.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

MissingRangeCheck.java
13/Dec/11 23:03
4 kB
Dag H. Wanvik
derby-5536-refactor.diff
10/Jan/12 07:41
6 kB
Dag H. Wanvik
derby-5536-3.stat
09/Jan/12 09:21
0.2 kB
Dag H. Wanvik
derby-5536-3.diff
09/Jan/12 09:21
12 kB
Dag H. Wanvik
derby-5536-2.stat
04/Jan/12 18:53
0.2 kB
Dag H. Wanvik
derby-5536-2.diff
04/Jan/12 18:53
11 kB
Dag H. Wanvik
derby-5536.stat
20/Dec/11 03:21
0.2 kB
Dag H. Wanvik
derby-5536.diff
20/Dec/11 03:21
10 kB
Dag H. Wanvik

Issue Links

relates to

DERBY-5533 Client differs from embedded when rs.updateInt overflows: 22015 vs 22003

Closed

Activity

People

Assignee:: Dag H. Wanvik

Reporter:: Dag H. Wanvik

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 13/Dec/11 23:02

Updated:: 07/Aug/13 17:08

Resolved:: 09/Jan/12 10:21