---- Reported by email@example.com 2009-04-27 20:41:16 ----
Fines are summing off by 1 penny due to rounding issue when summing.
This only occurs when summing many many records. The round off error occurs in the summation.
There is a multiplicand of 100 and then a divisor of 100. To ensure the summation will work for many fines, just make the multiplicand 1000 and the divisor 1000.
If there is still a problem with this, then bump it to 10000.
---- Additional Comments From firstname.lastname@example.org 2009-04-27 20:43:45 ----
Darrell, do you have an example in your database that I can look at?
---- Additional Comments From email@example.com 2009-04-30 22:26:33 ----
I think the proper way to do this is to do integer math. Do we really need to support more than two decimal places ? If so,
I suggest a system preference for CurrencyDecimalPlaces and a fcn C4::Output::as_currency(). (Or C4::Koha::).
The db will then always hold an integer value of 'cents' (or amount * 10^(CurrencyDecimalPlaces) ).
---- Additional Comments From firstname.lastname@example.org 2009-07-22 14:04:28 ----
Patch sent again! :) Simple one. Please accept. Occurs with patrons with long list of fines.
---- Additional Comments From email@example.com 2009-07-22 14:27:45 ----
Pushed patch. Bug should remain open, as we should switch to purely integer math as Ryan suggests.
--- Bug imported by firstname.lastname@example.org 2010-05-21 01:07 UTC ---
This bug was previously known as _bug_ 3166 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3166
Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
an account here. Reassigning to the person who moved
it here: email@example.com.
Previous reporter was firstname.lastname@example.org.
CC member email@example.com does not have an account here
CC member firstname.lastname@example.org does not have an account here
CC member email@example.com does not have an account here
CC member firstname.lastname@example.org does not have an account here
1- can't find the patch
2- can't find/imagine which script is concerned
=> hard to decide wether we should close this bug or not. Any idea someone ?