[jira] [Commented] (METAMODEL-141) Mapping of DOUBLE ColumnType to database-specific variant in JDBC module

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

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

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

Great source of inspiration for the column type mapping:
http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems
(the table named 'Data types')

> Mapping of DOUBLE ColumnType to database-specific variant 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)