empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Closed] (EMPIREDB-4) Bugs inside the DBDatabaseDriverHSql class
Date Mon, 04 Feb 2013 14:00:16 GMT

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

Rainer Döbele closed EMPIREDB-4.
--------------------------------


Cleanup of unclosed issues.
                
> Bugs inside the DBDatabaseDriverHSql class
> ------------------------------------------
>
>                 Key: EMPIREDB-4
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-4
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.0.3-incubating
>            Reporter: Jörg Reiher
>             Fix For: empire-db-2.0.3-incubating
>
>
> - The SQL_CONCAT_EXPR "+" leads to problems if operands are case when statements that
return empty strings in HSQL: The concatenated string is always null!
> - There's no "to_char()" function in HSQLDB that takes NUMBER and FORMAT string as parameters,
so an error should be thrown if this type of function is called on the HSQL driver
> - drop relation doesn't work as expected for HSQL: It doesn't prefix "ALTER TABLE DROP
CONSTRAINT" to the drop statement
> - INTEGER and AUTOINC db columns should be an 8 byte value
> - data type DATETIME gets translated to only Date (without time information)
> - data type CLOB gets translated to CLOB, but in HSQLDB it's called LONGVARCHAR
> - data type BLOB gets translated to BLOB, but in HSQLDB it's called LONGVARBINARY

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message