Pat Eyler <pate@eylerfamily.org> wrote:
Well, we may have some additional issues to deal with here, what about currency with no decimel part, or currencies with different kinds of units (do any of these still exist?). Perhaps we need to store currency in two fields (curr_major and curr_minor) with names controlled by (curr_major_name and curr_minor_name). Then we can ask for data to be
Only two? Why not have a curr_elements linked list table (four elements, called id, unit, amount, next_id) and then enter the id of the highest valued currency unit used in the cost column. The names would be controlled by curr_name, a reference into a chain in the curr_names table describing a linked list of currencies, least valued first and how many of them before we are worth one of the next most highly valued unit. Then koha purchases can handle all currencies, no matter how many units they have in the system. After that, we can add a table that describes the accounting worth of the various things that libraries may barter for fines and purchases. Or maybe we pick one basic unit for each exchange and use decimals relative to them. Your choice ;-) MJR