[ https://issues.apache.org/jira/browse/CALCITE-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044870#comment-17044870 ]
Vineet Garg commented on CALCITE-3734: -------------------------------------- bq. let's add a mechanism to add per-provider, per-datatype limits. Looks like this mechanism is already added with CALCITE-2713 > 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 > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > 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)