From 52bab2680c80c335e884f1696255025cc50a113f Mon Sep 17 00:00:00 2001 From: Pieterjan Spoelders Date: Tue, 2 Apr 2024 10:56:54 +0200 Subject: [PATCH] Update exasol.md Improved documentation on data type mismatches. --- doc/dialects/exasol.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/dialects/exasol.md b/doc/dialects/exasol.md index ca8bce9..dd58183 100644 --- a/doc/dialects/exasol.md +++ b/doc/dialects/exasol.md @@ -116,7 +116,11 @@ IMPORT INTO (c1 DECIMAL(36,1), c2 .... ) FROM EXA AT "EXA_CONNECTION" STATEMENT ##### Data type mismatch -In case you run into a `Data type mismatch` issue when using EXA import turning this property on will usually also solve the issue by providing type hints. +In case you run into a `Data type mismatch` issue which looks like this: +`Adapter generated invalid pushdown query for virtual table : Data type mismatch in column number (1-indexed).Expected , but got .` + +You can set the datatype mapping to true: `GENERATE_JDBC_DATATYPE_MAPPING_FOR_EXA = 'true'`. +This will usually solve the issue by providing type hints. ### Using `IMPORT FROM JDBC`