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] Created: (EMPIREDB-94) Postge and Derby bigint
Date Thu, 23 Dec 2010 09:05:01 GMT
Postge and Derby bigint
-----------------------

                 Key: EMPIREDB-94
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-94
             Project: Empire-DB
          Issue Type: Improvement
          Components: Core
    Affects Versions: empire-db-2.0.7-incubating 
            Reporter: Francis De Brabandere
             Fix For: empire-db-2.1.0-incubating


>From mails of Eike Kettner 2010/12/22

Hello,

I have a question regarding the integer type and ddl script generation.
I'm using empire-db with postgre-sql and apache derby. I'd like the
primary keys to be BIGINT and not INT and I didn't find a good way how
to tell empiredb when to use BIGINT and when to use INT - the datatype
is DataType.INTEGER and the drivers for postgre and derby do always say
INT (not sure about the newest trunk version).

What I do is overwriting the method

 boolean appendColumnDesc(DBTableColumn c, StringBuilder sql, boolean alter)

of the DBDatabaseDriver class and checking for an given size. So a
column with DataType.INTEGER and size=8 is then created as BIGINT.

Did I miss something, or how would you recommend to address this?

Thanks in advance
Eike

----

here is the patch. I modified the appendColumnDesc() method of the
postgresql and derby driver so it suits my needs. I ran some example
code against postgresql 8.4.5 and apache derby 10.6.2 - created the
database, inserted some data and executed some selects.

hope this is of some help.

kind regards,
Eike

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message