EXASOL: Ambiguous `{{ ... }}` from Jinja vs LUA

How to turn off Jinja templating? In LUA language its possible to use {{}}. this is parsed as Jinja

Originally from @sti0 in #684

I think if a user was using EXASOL + Jinja, that user would have to Jinja escape the section that includes {{ ... }}.

Otherwise do we have the option today of having no templater, maybe that is something we want to support ?

[sti0]

As I said. This only works if I use sqlfluff / Jinja engine. If I simply like to parse a given script for validating and automatic deployment (which is my use case) than the script don’t need Jinja. The script maybe needs to be processed in plain definition in some case with no need to parse it in sqlfluff first.

[sti0]

I think if a user was using EXASOL + Jinja, that user would have to Jinja escape the section that includes {{ ... }}.

But that will only work if using sqlfluff. If I parse a given LUA script it’s not parsable or ended up in a wrong result. I strongly recommend to turn off templating Exasol scripts. As it’s lua/ python/java there could be templating code inside.