https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41125 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #4)
I have used variables many times in past reports, but doing it without the SET command makes it more difficult. When we added the ability to call the exact same parameter multiple times, this was a reasonable workaround, but really bloats the code.
Instead of having a SET command, if maybe we had some options in the report setup to define some variables that could be "SET" when run, that could be helpful, and limit the use of the SET command.
So these don't work the way people think they do. "Note: The @VARIABLE:= syntax is a feature of MySQL/MariaDB databases separate from Koha. These are database session variables which can act differently than intended if not used very carefully." https://wiki.koha-community.org/wiki/SQL_Reports_Library#Runtime_Variables Likewise SET can affect the operation of the server or the client. It can be user-defined variables but it can also be a whole lot of other things which a Koha user should never ever be allowed to touch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.