https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16942
Jonathan Druart <jonathan.dru...@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=17246 --- Comment #19 from Jonathan Druart <jonathan.dru...@bugs.koha-community.org> --- (In reply to Kyle M Hall from comment #17) > I looked into this and it's working exactly as intended! Basically, the > tables hashref is a list of key/value pairs. The value can either be a) a > hashref or b) an arrayref. If it is a hashref, the keys are pulled out as > would be expected, based on the key name. For the arrayref, they simply need > to be ordered correctly. In the case of Holds, the lookup key is the fk > combo borrowernumber/biblionumber, in that order. I'd suggest to remove this behavior and only supports hashref, would you agree? See bug 17246. -- 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/