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] [Commented] (EMPIREDB-215) Sequence generation and use for HSql to not agree in using toUpperCase
Date Mon, 27 Oct 2014 10:34:34 GMT

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

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

Would you agree to just remove the uppercasing in DBDatabaseDriverHSql? It's up to the user
to decide what the sequence name should be.

> Sequence generation and use for HSql to not agree in using toUpperCase
> ----------------------------------------------------------------------
>
>                 Key: EMPIREDB-215
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-215
>             Project: Empire-DB
>          Issue Type: Bug
>    Affects Versions: empire-db-2.4.3
>         Environment: hsqldb-2.3.2
>            Reporter: Harald Kirsch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> {{DBDatabaseDriverHSql}} line 236 and
> {{HSqlDDLGenerator}} line 99
> do not agree in converting {{seqName}} to uppercase. The result is an SQL error when
the sequence is really used.
> This happens with hsqldb-2.3.2.
> Workaround: tables using sequences should have an uppercase name as well as all sequence
columns in uppercase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message