[jira] [Updated] (CALCITE-1684) Change default precision of VARCHAR and VARBINARY from 1 to "unspecified"

["Julian Hyde (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde updated CALCITE-1684:
---------------------------------
    Summary: Change default precision of VARCHAR and VARBINARY from 1 to "unspecified"  (was: Set the precision for VARCHAR and VARBINARY to the maximum value when not specified)

> Change default precision of VARCHAR and VARBINARY from 1 to "unspecified"
> -------------------------------------------------------------------------
>
>                 Key: CALCITE-1684
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1684
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.11.0
>            Reporter: Kevin Liew
>            Assignee: Julian Hyde
>            Priority: Minor
>             Fix For: 1.12.0
>
>
> The behavior for Calcite (and SQL Server) is to set {{VARCHAR}} precision to {{1}} when not specified whereas Phoenix sets the max integer value of {{2147483647}}.
> It doesn't really make sense to create a {{VARCHAR}} for a max length of {{1}} (it takes more bytes to store the length of each row than the actual value) and it shouldn't be the default behavior. I think we should adopt the Phoenix behavior. Do we need to make this configurable via SqlConformance or other?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)