https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10382
--- Comment #26 from Katrin Fischer <katrin.fisc...@bsz-bw.de> --- Hm, so is the problem that we save 'unchanged' instead of the original value, no matter if it was changed or not? And 'null' would be confusing, as it could mean 'unchanged' as well as 'was empty before'? So could it work like that? - change from a to b (changed, store a) - change from none to a (changed, store none) < current problem - change from a to none (changed, store a) - change from none to none (unchanged, store unchanged) - change from a to a (unchanged, store unchanged) I think the advantage of <unchanged> is currently that if you change the collection/location while the item is in the course reserve, with 'unchanged' it won't reset it by accident when you remove the item from the course reserve - the new value will stay. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
