Hi,
for small numeric columns, the ResultSetMetaData-Class seems to return wrong information for getPrecision and getColumnDisplaySize:
real precision getprecision getColumnDisplaySize
1 1 3
2 1 3
3 1 3
4 2 4
5 3 5
So the values for NUMERIC(1) and NUMERIC(2) seems to be wrong (we use the getColumnDisplaySize to get the precision for numeric and char columns).
Any ideas?
Thanks.
|
... anyone listening?
Thanks.
|
Sorry for missing that thread.
>So the values for NUMERIC(1) and NUMERIC(2) seems to be wrong (we use the >getColumnDisplaySize to get the precision for numeric and char columns).
It's a special process. Because DBF's NUMERIC(1) and NUMERIC(2) can be used to stor e decimal point and sign, so that their precision limited to 1.
|
... OK, so it is programatically not possible to get the precision
with which the column was created? Or is there another API or function?
Thanks in advance.
|
|
Yeah. It's a confusion for us too, because DBF numeric format won't consider store space for the decimal point and sign, so that it will result issue when convert to other database format.
|
Main
webmaster@hxtt.com