[10.1.264 Pro] - Preprocessor

[10.1.264 Pro] - Preprocessor

The SQL: Preprocessor pane has two parts. The upper one contains the Global defines. The lower part seems to be some kind of processing log message container:

However, sometimes there are no messages there even though there's surely some processing done. Is this by design?

I have asked the team for help with this issue, as I'm unable to explain the result

Turned out that the issue is in the code. There should be no space between -- and # and/or /* and #
that's why the second example didn't produce the expected results.

You might want to add that info as a Tip to User Guide explicitly stating there must not be any spaces between the comment marker (-- or /*) and the #. Though all the examples are made that way, it doesn't say it cannot have a space in between and adding a space there might be muscle memory for everyone working with MySQL which gets itchy when -- is followed by anything else but space and # in this case (but preprocessor is SA specific thing, not MySQL, so that might not be that obvious).

Also, it seems that SA struggles maintaining a clear view of the status of those macros. Check this short video >>>here<<<. At first, everything is good, but then I introduce an error into the third #define which is caught and it no longer recovers from that error. It requires a reconnect to make things good again.

Last edited by gemisigo on Wed Feb 06, 2019 10:40 am; edited 1 time in total

Many thanks for the video demonstrating the issue and for the tip for the User's Guide.

The issue is not specific to SQL Preprocessor. It's caused by a bug in a different place, there is an incorrect handling of SQL warnings, "SHOW WARNINGS" clears only warnings and keeps diagnostic errors, which get stuck somewhere. We are planning a hot fix for this and a couple of other issues, tentatively scheduled for next week.