I just tested the new versión of Ocilib 3.12 and I found an error in OCI_GetString. I've got a table with columns defined like NUMBER(4). When I try to get values from these columns OCI_GetString return me values like "4." (with point at the end). I tested the versión 3.10 and it Works fine.
Yours sincerely
Josemi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right. Some code to remove trailing comma and dot in number to string conversions has been removed by mistake in 3.11.0. I will make a 3.12.1 release asap.
Sorry about that....
Last edit: Vincent Rogier 2013-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The bug only occurs when using OCI_CHARSET_WIDE or OCI_CHARSET_MIXED builds
of OCILIB.
in version 3.10.00, the removal of trailing dots and commas was not removed
but failed as the number of character of the converted string was not
correctly computed when using unicode user strings...
number.c, line 414 :
out_value_size = osize1;
should be replaced by
out_value_size = (osize1 / (int) sizeof(dtext));
Last edit: Vincent Rogier 2013-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Vincent
I just tested the new versión of Ocilib 3.12 and I found an error in OCI_GetString. I've got a table with columns defined like NUMBER(4). When I try to get values from these columns OCI_GetString return me values like "4." (with point at the end). I tested the versión 3.10 and it Works fine.
Yours sincerely
Josemi
hi,
You are right. Some code to remove trailing comma and dot in number to string conversions has been removed by mistake in 3.11.0. I will make a 3.12.1 release asap.
Sorry about that....
Last edit: Vincent Rogier 2013-02-25
Hi,
The bug only occurs when using OCI_CHARSET_WIDE or OCI_CHARSET_MIXED builds
of OCILIB.
in version 3.10.00, the removal of trailing dots and commas was not removed
but failed as the number of character of the converted string was not
correctly computed when using unicode user strings...
number.c, line 414 :
out_value_size = osize1;
should be replaced by
out_value_size = (osize1 / (int) sizeof(dtext));
Last edit: Vincent Rogier 2013-02-25