You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Kevin Liew (JIRA)" <ji...@apache.org> on 2017/03/09 00:49:38 UTC

[jira] [Created] (CALCITE-1684) Default precision for VARCHAR should be the maximum value

Kevin Liew created CALCITE-1684:
-----------------------------------

             Summary: Default precision for VARCHAR should be the maximum value
                 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


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)