http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7303
--- Comment #8 from Katrin Fischer <[email protected]> --- Hi Jonathan and all, I still think a unique key on aqbudgets.budget_name and aqbudgets.budget_code it's a bad idea and will break workflows for libraries. 1) The aqbudgets table already has a primary key (budget_id) as has aqbudgetperiods (budget_period_id). 2) It will make it impossible to duplicate your budget hierarchy for the next year which is a working feature in master. 3) A feature I am asked for is a way to move orders and money from one year to the next. I think if it's allowed to use the same codes, this is very easy to do - but if you are forced to change them each year, you will need some tool for mapping funds over several years. 4) The codes libraries here use do not change with each year - you would force them to add a prefix/suffix or something similar. This would make their life harder, for example when they need reports with the official codes and descriptions. 5) It's currently not enforced - I think the update database will not work? If this is only a check for libraries editing/adding new funds, couldn't we make it only check for duplicates in the same time period/budget? And a way to overwrite if it's intended? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
