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 | Low |
| Complexity | Unknown |
| Component | Editor - Debugger for Sybase |
| Version | 16.0 |
Default Format values missing Sybase Procedure Debugger unsigned bigint, int and smallint
To reproduce
made needed changes, waiting on jenny's review...
I tested the changes, but the Format for the Unsigned Bigint parameter is displayed as ###0.00 instead of ###0. Is that correct?
I tested the changes, but the Format for the Unsigned Bigint parameter is displayed as ###0.00 instead of ###0. Is that correct?
In datastudio 16 we are using java 1.6 and an unsigned bigint is bigger then a signed long by one bit, so we represent it with bigdecimal. I believe this should either be represented by java biginteger class, though we had an issue prior that stated we will never map datatypes to java biginteger. In Java SE 8 and later, you can use the long data type to represent an unsigned 64-bit long, so perhaps we should revisit unsigned biginteger mappings in version 18 and map them to unsignedlong class. The issue that having it as a bigdecimal is that its format is constructed as ###0.00 instead of ###0
Will file a separate issue for this for future release...
In datastudio 16 we are using java 1.6 and an unsigned bigint is bigger then a signed long by one bit, so we represent it with bigdecimal. I believe this should either be represented by java biginteger class, though we had an issue prior that stated we will never map datatypes to java biginteger. In Java SE 8 and later, you can use the long data type to represent an unsigned 64-bit long, so perhaps we should revisit unsigned biginteger mappings in version 18 and map them to unsignedlong class. The issue that having it as a bigdecimal is that its format is constructed as ###0.00 instead of ###0
Will file a separate issue for this for future release...
changes made to capture datatype info correctly from driver
changes made to capture datatype info correctly from driver
Patch is approved. Ready for check-in.
Patch is approved. Ready for check-in.
Verified in ADS v16.0.9-3 and in 17.0.0-rc-12
Verified in ADS v16.0.9-3 and in 17.0.0-rc-12
Verified this issue using below sql script:
Verified this issue using below sql script:
Issue #13777 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.9-3 |
| No time estimate |
1 issue link |
relates to #13780
Issue #13780Default Format values missing in Oracle Procedure Debugger for LONG, BFILE,CLOB,BLOB |
made needed changes, waiting on jenny's review...