https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16002
--- Comment #6 from Christopher Brannon <[email protected]> --- (In reply to Katrin Fischer from comment #1) > Hi Christopher, I think the problem is in how to make this work with the SQL > query. <<branches>> is usually used with =, multi could be used with 'in > (....)', but not sure how how to make an 'all' work in a good way. It seems like if you could do something like: homebranch IN (<<Branch|branches:all>>) If Koha could detect the parameter was in an IN statement, maybe it could use a dropdown that allows multiple selections. And if the all selection is made, all the selections would be in the IN statement. There would just need to be some logic to handle what to do if ALL was one of the multiple selections so it doesn't create strange results. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
