sqllogictest statement error no escaping

[aprimadi]

Is your feature request related to a problem or challenge?

Currently ( and ) character needs to be escaped in sqllogictest statement error. Not sure if this is possible but it would be great if I can just supply a string that is an exact match of the output and not need to escape the character.

Expected

statement error ParserError("blablabla")

Current

statement error ParserError\("blablabla"\)

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[alamb]

FYI @melgenek -- this seems very similar to #5727

I wonder if we can apply a similar fix 🤔

[melgenek]

it would be great if I can just supply a string that is an exact match of the output and not need to escape the character.

If I understand correctly, there is no issue at the moment, and validation works correctly when symbols are escaped.

sqllogictest-rs makes an explicit choice to have errors as Regexp, that's why there is a need to escape characters that have special meaning in Regex like (,),.,[,]

[alamb]

I think I have seen errors (maybe where newlines aren't escaped?) I'll pay attention to this in more detail if it happens again

[alamb]

Closing this ticket as working as expected, I think