Bad storage of Numeric values [CORE1350] #1769
Comments
|
Commented by: @dyemanov What is the database dialect? It looks like it's Dialect 1. It you want exact numerics, you should be using Dialect 3, otherwise all numerics are approximate. |
|
Commented by: @pcisar This is expected and well documented behaviour for legacy SQL DIALECT 1 databases. Exact (large) numerics require SQL DIALECT 3, which is the default dialect for new databases since Firebird 0.9. |
|
Commented by: Martin Pavlik (quitec) Yes, I use SQL dialect 1 in this case. |
Modified by: @pcisarWorkflow: jira [ 12530 ] => Firebird [ 14143 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Martin Pavlik (quitec)
Numeric values are stored with higher precision than declared. Such values are not visible by a simple select, but become visible when multiplied by a bigger number.
Example:
- declaration of variable N in table T is Numeric(15,2)
- update T set N =0.001234 where ID=1 sets variable to an invisible value
- select N from T where ID=1 returns 0.00 as expected
- select N*10000 from T where ID=1 returns 12.34 which is WRONG!
This gives unexpected results for example when calculating unit price * volume = total price,
because 0.00 * something should be 0.00 and not something else.
The text was updated successfully, but these errors were encountered: