[
https://issues.apache.org/jira/browse/METAMODEL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694088#comment-14694088
]
ASF GitHub Bot commented on METAMODEL-143:
------------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/metamodel/pull/25
> Escape/normalize column names in create table operations
> --------------------------------------------------------
>
> Key: METAMODEL-143
> URL: https://issues.apache.org/jira/browse/METAMODEL-143
> Project: Apache MetaModel
> Issue Type: Bug
> Reporter: Kasper Sørensen
>
> For many applications (at least the one I am working on ;-)) the column names
> in a MetaModel CREATE TABLE operation may be dynamically provided for
> instance by the UI or by some other mechanism in the application. For those
> external parts it may be close to impossible to figure out if a particular
> column name is valid or not. For instance in JDBC databases it's typically
> not allowed with whitespaces in column names, whereas it is allowed in some
> NoSQL and file-based datastores.
> Wouldn't it be smarter then that we make this validation (and potential
> on-the-fly normalization) a responsibility of the backing DataContext. For
> instance, in JDBC module we could ensure that whitespace is replaced by
> underscore and that other special characters maybe also get some special
> treatment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
