metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Sørensen (JIRA) <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-141) Automatic datatype mapping in JDBC module
Date Mon, 18 May 2015 18:02:00 GMT

    [ https://issues.apache.org/jira/browse/METAMODEL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548414#comment-14548414
] 

Kasper Sørensen commented on METAMODEL-141:
-------------------------------------------

Hmm actually I see that this feature is already here via the {code}IQueryRewriter.rewriteColumnType{code}
method. So I will rephrase the story to deal specifically with the DOUBLE type which I encountered.

> Automatic datatype mapping in JDBC module
> -----------------------------------------
>
>                 Key: METAMODEL-141
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-141
>             Project: Apache MetaModel
>          Issue Type: Improvement
>            Reporter: Kasper Sørensen
>
> I am right now running into a issue that I have seen in various different styles: I am
executing a CREATE TABLE operation with MetaModel where one of the data types is ColumnType.DOUBLE.
It works on some databases but for instance on MS SQL Server it crashes because there is no
DOUBLE type on SQL server. Instead there's a NUMERIC type that could be used to hold the same
information. So it would be very nice if MetaModel could do a database-vendor specific datatype
conversion so that the same CREATE TABLE statement can be applied to multiple datastores.



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

Mime
View raw message