Subject | Re: 4.3aa bug(?) with float fields |
---|---|
Author | pict100 |
Post date | 2004-02-15T08:14:49Z |
We had a similar problem until we changed all
double precision fields into numeric(18,4)
It may be something else in your application.
The fastest way to change all this was to
declare a new domain :
CREATE DOMAIN "T_CURRENCY" AS NUMERIC(18, 4);
and in metadata now we have :
"CREDIT" T_CURRENCY ,
INSTEAD OF
"CREDIT" DOUBLE PRECISION,
Now it works flawlessly.
Hope that helped
Nx
double precision fields into numeric(18,4)
It may be something else in your application.
The fastest way to change all this was to
declare a new domain :
CREATE DOMAIN "T_CURRENCY" AS NUMERIC(18, 4);
and in metadata now we have :
"CREDIT" T_CURRENCY ,
INSTEAD OF
"CREDIT" DOUBLE PRECISION,
Now it works flawlessly.
Hope that helped
Nx