New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameters not working when using complex filters #41
Comments
Forgot to add, when replacing the parameter in the filter expression with the actual value I'm assigning the parameter, I can export the data successfully. |
Thanks for the report. I will have a look at it as soon as possible. |
Many thanks Wisser! |
The reason for this was that the SQL formatter unfortunately inserted spaces in awkward places. |
That was quick! Thanks a bunch., I'll download 10.4 and give it a try :) I'm already loving this tool, has saved me a bunch of time for moving data around. |
Description of the Issue
When adding parameters to certain filter expressions (Whether that's through templates or direct ones), the parameter gets blank space characters added to it, rendering it useless as jailer won't recognize it as a parameter anymore , with a failed export as the result.
I noticed that this bug is only visible when opening the expression editor (Apart from the error log output), viewing it "inline" or directly displays the parameter correctly:
I attempted many different combinations, (My real filter expressions has lots of concatenation operators), but even simple ones as the example above fails. The only expressions I could get consistent working results with are ones where the full expression is solely the parameter name itself.
Other things that did not help:
Expected Behavior
At save, runtime & edit, one expects the parameter to stay the way it was written out when closing the editor.
Actual Behavior
Parameters are changed into: $ { to_plc_id } from: ${to_plc_id}.
Debug Information
Windows 10 1909
Jailer 10.3.5
The text was updated successfully, but these errors were encountered: