You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2011/02/01 16:38:28 UTC

[jira] Commented: (EMPIREDB-100) Support of long integer fields

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

Francis De Brabandere commented on EMPIREDB-100:
------------------------------------------------

hey Eric, thanks a lot for the rest case! In fact that don't forget was more for us at a team than especially for you :-)

I'll try to have this committed and fixed by the end of the week.

> Support of long integer fields
> ------------------------------
>
>                 Key: EMPIREDB-100
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-100
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.0.6-incubating
>            Reporter: Eric Cournarie
>             Fix For: empire-db-2.1.0-incubating
>
>         Attachments: App.java
>
>
> When defining a integer column with a size of 8 for holding a long value, it generates a SQL with INT(8) which is not understand. Most databases use rather BIGINT (and SMALLINT for short values). This is true at least for H2, Derby, MySQL.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira