Parse error for queries is not specific enough

[blcham]

In a module such as ApplyConstruct, when it fails due to a parse error, it says something like:

The issue is that I am not able to find out why the parse error occurred, as I do not see the original query. The query should be logged as well (or maybe even pointing somehow to where the error exactly occurs so the user does not necessarily need to use an external editor to find it out from the line/column number).

A/C:

• within "this issue thread", it is shown how logging of parse error looked before and how it looks now so I can compare
• parse error related to validation constraints is improved as well and shown here

[blcham]

You can test it on pipeline https://github.com/kbss-cvut/s-pipes/blob/54dfb128d59584980a78be036965ab089d164dfa/doc/examples/hello-world/hello-world.sms.ttl#L53C1-L53C1 as follows:

1. deploy Spipes
2. run script hello-world
3. modify apply construct in https://github.com/kbss-cvut/s-pipes/blob/54dfb128d59584980a78be036965ab089d164dfa/doc/examples/hello-world/hello-world.sms.ttl#L53C1-L53C1 to make parse error in the query
4. run script hello-world again to see the parse error -- AND this is what needs to be improved

[blcham]

Another queries (validation queries) can be tested here

[MSattrtand]

How the log looks now using the constraint validation as an example:


The image is split into two parts because the displayed query is long.

[MSattrtand]

Logs now output incorrect line when QueryParseException happens. Examples: