Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | DB - Sybase ASE |
| Version | 17.0 |
[Err] message is been displayed when working with unsigned big integers that have values that exceed the range of java long types.
example:
create table test_unsigned (ubi unsigned bigint primary key, bi bigint, i int, ui unsigned int) go insert into test_unsigned values (0x123456, 1, 123, 4294967295) go insert into test_unsigned values (0xFFFFFFFFFFFFFFFF, 2, 123, 123123) go select * from test_unsigned // results /* ubi bi i ui ------- ----- ---- ---------- 5649426 1 123 4294967295 [Err] 2 123 123123 */
The jdbc driver is returning the type as bigint for both unsigned and signed bigintegers. Because of this we need to force bigint to the BigInteger java type instead of the java long type.
reverted code in v18 till further review of impact is completed on v19
reverted code in v18 till further review of impact is completed on v19
After further review, bigint will still map to java long. The driver returns the type as BigInt for both unsigned and signed bigint types. The class is returned as bigdecimal for the unsigned and long for the signed. For the purposes of the query analyzer we will map bigint type to unsigned bigint type when the driver returns the class as java.math.BigDecimal. Committed revision: 54735
After further review, bigint will still map to java long. The driver returns the type as BigInt for both unsigned and signed bigint types. The class is returned as bigdecimal for the unsigned and long for the signed. For the purposes of the query analyzer we will map bigint type to unsigned bigint type when the driver returns the class as java.math.BigDecimal. Committed revision: 54735
@ivan: once this issue is verified, pls back port to ADS v17
@ivan: once this issue is verified, pls back port to ADS v17
Works fine in ADS v19.0.0-alpha-42 in Query Analyzer, Query Builder, FluidShell and VA. Please port to v17 as well
Works fine in ADS v19.0.0-alpha-42 in Query Analyzer, Query Builder, FluidShell and VA. Please port to v17 as well
Reopening this issue as bigint is displayed as a string in Measure pane which is incorrect.
This is broken in alpha-42.
Works fine in alpha-40.
Column having bigint datatype should be treated as measures.
Refer attached screenshot(15316_alpha-42.png)
Reopening this issue as bigint is displayed as a string in Measure pane which is incorrect.
This is broken in alpha-42.
Works fine in alpha-40.
Column having bigint datatype should be treated as measures.
Refer attached screenshot(15316_alpha-42.png)
@qa: pls test again in 19.0.0-alpha-43 & 18.0.14-7
@qa: pls test again in 19.0.0-alpha-43 & 18.0.14-7
code has been ported back to version 17 with Commit revision : 54764
code has been ported back to version 17 with Commit revision : 54764
The fix did not carry to the Fluidshell part. See attached screenshot. It worked fine in alpha-42 but broken in alpha-43, v18.0.14-7 and 17.0.13-1
The fix did not carry to the Fluidshell part. See attached screenshot. It worked fine in alpha-42 but broken in alpha-43, v18.0.14-7 and 17.0.13-1
Verified the issue in 18.0.15 & 19-alpha-45.
All above datatypes are displayed as Measures in Measure pane.
Refer attached screenshot(Sybase ASE_bigint.png)
Verified the issue in 18.0.15 & 19-alpha-45.
All above datatypes are displayed as Measures in Measure pane.
Refer attached screenshot(Sybase ASE_bigint.png)
The fluid shell uses a different context class. I have made changes to the fluid shell context class so that unsigned int and unsigned bigint are correctly handled in sybase ase. Code checked in to US trunk, version 18 & version 17 with Commit revisions: 54774, 54775, 54776
The fluid shell uses a different context class. I have made changes to the fluid shell context class so that unsigned int and unsigned bigint are correctly handled in sybase ase. Code checked in to US trunk, version 18 & version 17 with Commit revisions: 54774, 54775, 54776
Verified in ADS v17.0.13-2. Pending tests in 19.0.0-alpha-48 & ADS v18.0.15-2
Verified in ADS v17.0.13-2. Pending tests in 19.0.0-alpha-48 & ADS v18.0.15-2
Issue #15316 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v19.0.0-alpha-48, v18.0.15-2, 17.0.13-2 |
| No time estimate |
The jdbc driver is returning the type as bigint for both unsigned and signed bigintegers. Because of this we need to force bigint to the BigInteger java type instead of the java long type.