empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] Updated: (EMPIREDB-100) Support of long integer fields
Date Tue, 01 Feb 2011 08:19:28 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Francis De Brabandere updated EMPIREDB-100:

    Fix Version/s: empire-db-2.1.0-incubating

Thanks ecournarie,

I think this has been taken care of for derby in 2.0.7, see EMPIREDB-94

We should probably migrate that code to the other drivers you mention. Don't forget to write
a test for at least H2 and derby as we can run those embedded.

> 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
> 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


View raw message