[
https://issues.apache.org/jira/browse/CALCITE-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016269#comment-17016269
]
Julian Hyde commented on CALCITE-3734:
--------------------------------------
The 255 limit for CHAR is MySQL-specific (Vertica, for example, allows up to
65000 bytes). So, as part of this fix, let's add a mechanism to add
per-provider, per-datatype limits.
> MySQL JDBC rewrite is producing queries with CHAR with range beyond 255
> -----------------------------------------------------------------------
>
> Key: CALCITE-3734
> URL: https://issues.apache.org/jira/browse/CALCITE-3734
> Project: Calcite
> Issue Type: Bug
> Components: jdbc-adapter
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
>
> Queries containing cast to varchar/string is rewritten into cast to CHAR with
> range beyond 255 causing query failure. This range/precision should be
> limited to 255.
> I will provide a test case later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
