Symptom
- Wrong numeric value inserted in table when using jconnect
- See below some outputs..
Using batch to update null decimal values and non decimal values to not null (ID 1: setBigDecimal, ID 2: setDouble)
ID: 1 should be: 12345.54321, was (double): 12345.54321
ID: 1 should be: 12345.54321, was (big decimal): 12345.54321
ID: 2 should be: 12345.54321, was (double): 0.12345
ID: 2 should be: 12345.54321, was (big decimal): 0.12345
Using batch for updating null decimal value to non null in other row and non decimal value to non null value in other row
ID: 3 should be: null, was (double): 0.0
ID: 3 should be: null, was (big decimal): null
ID: 4 should be: 12345.54321, was (double): 1.234554321E9
ID: 4 should be: 12345.54321, was (big decimal): 1234554321.00000
Updating row by row null decimal value to not null using null value for non decimal value
ID: 5 should be: null, was (double): 0.0
ID: 5 should be: null, was (big decimal): null
ID: 6 should be: 12345.54321, was (double): 12345.54321
ID: 6 should be: 12345.54321, was (big decimal): 12345.54321
Reusing same PreparedStatement to update null decimal value to non null in other row and non decimal value to non null value in other row
ID: 7 should be: null, was (double): 0.0
ID: 7 should be: null, was (big decimal): null
ID: 8 should be: 12345.54321, was (double): 1.234554321E9
ID: 8 should be: 12345.54321, was (big decimal): 1234554321.00000
Read more...
Environment
- SAP ASE Software Development Kit (SDK) 15.7 SP120 -- Jconnect 7.07
Product
Keywords
KBA , BC-SYB-SDK , SDK , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.