[jira] Resolved: (EMPIREDB-4) Bugs inside the DBDatabaseDriverHSql class

["Jörg Reiher (JIRA)" <em...@incubator.apache.org>]

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

Jörg Reiher resolved EMPIREDB-4.
--------------------------------

    Resolution: Fixed

- 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!
-> Replaced SQL_CONCAT_EXPR by HSQLDB "concat()" function

- 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
-> Now error gets thrown if you try to call this function

- drop relation doesn't work as expected for HSQL: It doesn't prefix "ALTER TABLE DROP CONSTRAINT" to the drop statement
-> added ALTER TABLE ... to statement construction

- 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 

-> Changed Empire-db data type to SQL data type mappings of HSQLDB drivers:
DataType.INTEGER -> BIGINT
DataType.AUTOINC -> BIGINT
DataType.CLOB -> LONGVARCHAR
DataType.BLOB -> LONGVARBINARY
DataType.DATETIME -> DATETIME


> 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.
-
You can reply to this email to add a comment to the issue online.