>The issue is not the encoding of our Java code. The issue is the encoding of the SQL we process. That SQL may or may not come from Java source files.
I can't remember another database that allows just ISO-8859-1 in simple string literals. That makes it very surprising. For instance, https://rextester.com/l/postgresql_online_compiler allows <<select 'привет'='привет' >> What is the reason for Calcite to enforce ISO-8859-1 by default? In other words, I can't imagine a project that would pick ISO-8859-1 as a default string literal encoding if they HAVE to make an explicit choice (e.g. no default within Calcite). Vladimir
