[
https://issues.apache.org/jira/browse/FLINK-24948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447848#comment-17447848
]
Jark Wu commented on FLINK-24948:
---------------------------------
[~Paul Lin] I think we need to fix the bug in the
FieldNamedPreparedStatementImpl.
> Special character in column names breaks JDBC statement parsing
> ---------------------------------------------------------------
>
> Key: FLINK-24948
> URL: https://issues.apache.org/jira/browse/FLINK-24948
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: 1.12.4
> Reporter: Paul Lin
> Assignee: Paul Lin
> Priority: Major
>
> Currently, JDBC connector assumes columns names respect Java identifier
> naming restrictions, but Databases that support JDBC may have different
> naming restrictions. For example, MySQL allows dots and colons in column
> names. In that case, JDBC connector would have trouble parsing the SQL.
> We could fix this by validating field names in `JdbcDmlOptions`. In addition,
> it'd be good to clarify the naming restrictions of Flink SQL, so users and
> connector developers would know the standard.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
