[
https://issues.apache.org/jira/browse/IGNITE-11434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809764#comment-16809764
]
Vladimir Ozerov commented on IGNITE-11434:
------------------------------------------
[~tledkov-gridgain], yes, as we support DEFAULT, let's leave it. But value
should be displayed through special function {{toStringSafe}}. As far as column
ID vs cache ID - this is not very accurate comparison. Cache ID was meant to be
internal thing, yet it leaked to the outside long time ago, and now widely used
in logs and utilities. So it is OK to have cache ID. Column ID is different -
we never exposed it to users. +1 to idea to expose ordinal instead.
> SQL: Create a view with list of existing COLUMNS
> ------------------------------------------------
>
> Key: IGNITE-11434
> URL: https://issues.apache.org/jira/browse/IGNITE-11434
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Taras Ledkov
> Priority: Major
> Labels: iep-29
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Need to expose SQL system view with COLUMNS information.
> Need to investigate more deeper which of information should be there.
>
> As start point we can take
> [https://dev.mysql.com/doc/refman/8.0/en/columns-table.html]
> Columns description:
> || Name || Type || Description||
> | SCHEMA_NAME | string | Schema name |
> | TABLE_NAME | string | Table name |
> | COLUMN_ID | int | Column ID |
> | COLUMN_NAME | string | Column name |
> | DEFAULT VALUE | string | Defaut column's value |
> | IS_NULLABLE | boolean | Nullable flag corresponds to
> {{QueryEntity#setNotNullFields}} |
> | SQL TYPE | int | SQL data type ID |
> | DATA_TYPE | string | SQL data type |
> | DISPLAY_SIZE| int | Size (e.g. for VARCHAR) |
> | PRECISION | int | Precision |
> | SCALE | int | Scale |
> | AFFINITY_KEY | boolean | {{true}} whan the column is affinity key |
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
