https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39622
--- Comment #1 from David Cook <[email protected]> --- I'm thinking that we could add an optional 2nd pipe (ie |) which lets you link runtime parameters together. Someone manually writing it could just do something like <<Start date|date|sdate123>> and use that same runtime parameter a couple of times in the query. With the "Insert runtime parameter" button, we might be able to do something clever in terms of auto-generating that linkage. Providing the friendly labels in a dropdown list, and just autogenerating the linking/tag value. -- I don't have a real plan for this, but it's just something that popped into my head while I was helping someone with a report involving runtime parameters for 1 date that has to be applied across different subqueries. I know we have "Runtime Variables" but those are actually MySQL/MariaDB session variables, and they can be problematic. Since they live beyond the life of that SQL query, it's always possible that they'll get re-used in a different SQL query. Or - as noted on the wiki - they can sometimes be optimized away. I've seen too many problems with these to really advocate for them for production data reports. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
