Subject | Re: [firebird-support] Re: Money data type |
---|---|
Author | Helen Borrie |
Post date | 2006-05-20T23:50:51Z |
At 05:30 AM 21/05/2006, you wrote:
two types of scaled integer and have a type DECIMAL that stores a
number with higher precision (the first argument in the declaration)
than that specified.
In Firebird there is no difference. Both decimal and numeric will
accept values up to the supported implementation limit without
over/underflowing.
plus any constraints you want to add.
interested to see if anything on this topic has changed recently and
increase in possible precision if/when Firebird supports 128-bit
integers - not currently on the radar.
Another thing that might come "some time" would be the ability to
have domain definitions available as "data types" for the input and
output arguments and local variables for stored procedures and
EXECUTE BLOCK constructs. Currently it's not possible, so you have
to take care that these variables match any domain-driven database
values they have to accommodate. But it is on the radar.
./heLen
>Could you please elaborate a bit more on the differences betweenUnder the SQL standard, it's possible to differentiate between the
>decimal and numeric and why I would want to "exceed the precision".
two types of scaled integer and have a type DECIMAL that stores a
number with higher precision (the first argument in the declaration)
than that specified.
In Firebird there is no difference. Both decimal and numeric will
accept values up to the supported implementation limit without
over/underflowing.
>What might the syntax look like to create the domain mentioned?create domain money as numeric(18,2)
plus any constraints you want to add.
interested to see if anything on this topic has changed recently and
>what is currently recommended. Also, has Firebird 2.0 introducedNo. The next "big thing" with fixed numeric types would likely be an
>anything new to consider on this topic?
increase in possible precision if/when Firebird supports 128-bit
integers - not currently on the radar.
Another thing that might come "some time" would be the ability to
have domain definitions available as "data types" for the input and
output arguments and local variables for stored procedures and
EXECUTE BLOCK constructs. Currently it's not possible, so you have
to take care that these variables match any domain-driven database
values they have to accommodate. But it is on the radar.
./heLen