[
https://issues.apache.org/jira/browse/FLINK-8551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352205#comment-16352205
]
Fabian Hueske commented on FLINK-8551:
--------------------------------------
If I understand the issue correctly, you are suggesting to change the default
behavior for {{BIGINT}} to match the behavior of MySQL.
I had a look a the docs of a few other RDBMS (PostgreSQL, SQL Server) and they
don't seem to have the option for unsigned {{BIGINT}}.
So this doesn't seem to be a feature that the systems agree about.
Why should we favor MySQL's design over others?
> Should BIGINT in Flink SQL will be enchanced
> --------------------------------------------
>
> Key: FLINK-8551
> URL: https://issues.apache.org/jira/browse/FLINK-8551
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.4.0
> Reporter: Lynch Lee
> Priority: Major
> Fix For: 1.4.0
>
>
> As we all known , see
> [https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-type-conversions.html]
> SQL data type BIGINT in mysql represents UNSIGNED BIGINT by default , it can
> receive value from some columns typed Long or BigInteger if we use java/scala
> driver to write data into db.
> ||MySQL Type Name||Return value of {{GetColumnTyneName}}||Return value of
> {{GetColumnClassName}}||
> |{{BIGINT[(M)] [UNSIGNED]}}|{{BIGINT [UNSIGNED]}}|{{java.lang.Long}}, if
> UNSIGNED {{java.math.BigInteger}}|
>
> But now , in Flink SQL BIGINT just represents SIGNED BIGINT, that to say it
> can only receive value from some columns typed Long .
> all supported types of the Table API defined in this class
> org.apache.flink.table.api.Types
>
> so if we should let BIGINT in Flink SQL match the BIGINT in some SQL Engine ,
> like MySQL.
> Or, as a new feature, support a new FLINK SQL type named BIGINTEGER for Java
> type Biginteger and also into MySQL BIGINT?
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
