drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (DRILL-3216) Fix existing INFORMATION_SCHEMA.COLUMNS columns
Date Mon, 01 Jun 2015 18:44:18 GMT

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

Daniel Barclay (Drill) updated DRILL-3216:
------------------------------------------
    Comment: was deleted

(was: Note:  Regarding INFORMATION_SCHEMA.COLUMNS.DATA_TYPE:

Need to analyze:
1) ISO/IEC 9075-2:2011(E) section 9.9, "Type name determination" (which defines some kind
of type name (an <identifier> return value) which uses short forms, e.g., "VARCHAR"),
and uses of (explicit or implement references to) it, versus 
2) DEFINITION_SCHEMA's DATA_TYPE_DESCRIPTOR base table's constraint  DATA_TYPE_DESCRIPTOR_DATA_TYPE_CHECK_COMBINATIONS
(which clearly requires long forms, e.g., 'CHARACTER VARYING').)

> Fix existing INFORMATION_SCHEMA.COLUMNS columns
> -----------------------------------------------
>
>                 Key: DRILL-3216
>                 URL: https://issues.apache.org/jira/browse/DRILL-3216
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Daniel Barclay (Drill)
>
> [Editing in progress]
> Change logical null from {{-1}} to actual {{NULL}}:
> - Change column {{CHARACTER_MAXIMUM_LENGTH}}.
> - Change column {{NUMERIC_PRECISION}}.
> - Change column {{NUMERIC_PRECISION_RADIX}}.
> - Change column {{NUMERIC_SCALE}}.
> Change column {{ORDINAL_POSITION}} from zero-based to one-based.
> Change column {{DATA_TYPE}} from short names (e.g., "CHAR") to specified names (e.g.,
"CHARACTER").
> Fix data type names "INTERVAL_DAY_TIME" and "INTERVAL_YEAR_MONTH" to "INTERVAL":
> - Change column {{DATA_TYPE}} to list "INTERVAL" for interval types.
> - Add column {{INTERVAL_TYPE}}.
> Move {{CHAR}} length from {{NUMERIC_PRECISION}} to {{CHARACTER_MAXIMUM_LENGTH}} (same
as {{VARCHAR}} length):
> - Change column {{NUMERIC_PRECISION}} from length to logical null for CHAR.
> - Change column {{CHARACTER_MAXIMUM_LENGTH}} from logical null to length for CHAR.
> Move {{BINARY}} and {{VARBINARY}} length from {{NUMERIC_PRECISION}} to {{CHARACTER_MAXIMUM_LENGTH}}
(same as CHAR and VARCHAR length):
> - Change column {{NUMERIC_PRECISION}} from length to logical null for BINARY and VARBINARY.
> - Change column {{CHARACTER_MAXIMUM_LENGTH}} from logical null to length for BINARY and
VARBINARY.
> To correct ordinal position of some existing columns:
> - Add column {{COLUMN_DEFAULT}}.
> - Add column {{CHARACTER_OCTET_LENGTH}}.
> - Reorder column {{NUMERIC_PRECISION}}.
> Move date/time and interval precisions from {{NUMERIC_PRECISION}} to {{DATETIME_PRECISION}}
and {{INTERVAL_PRECISION}}:
> - Change column {{NUMERIC_PRECISION}} to logically null for date/time and interval types.
> - Add column {{DATETIME_PRECISION}}.
> - Add column {{INTERVAL_PRECISION}}.
> Implement {{NUMERIC_PRECISION_RADIX}}:
> - Change column {{NUMERIC_PRECISION_RADIX}} from always logically null to appropriate
values (2, 10, NULL).
> Add missing numeric precision and scale values (for non-DECIMAL types):
> - Change NUMERIC_SCALE from logical null to zero for integer types.
> - Change NUMERIC_PRECISION from logical null to precision for non-DECIMAL numeric types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message