[ https://issues.apache.org/jira/browse/OPENJPA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688391#comment-13688391 ]
Di Wu Lau commented on OPENJPA-2391: ------------------------------------ Does anyone have objections to upgrade from hsql 1.x to 2.x? > HSQLDB v2.2.9 > ------------- > > Key: OPENJPA-2391 > URL: https://issues.apache.org/jira/browse/OPENJPA-2391 > Project: OpenJPA > Issue Type: Bug > Components: jdbc > Environment: OpenJDK Runtime Environment (fedora-2.3.9.5.fc18-i386) > OpenJDK Server VM (build 23.7-b01, mixed mode) > Apache Maven 3.0.4 (rNON-CANONICAL_2013-04-08_07-49_mockbuild; 2013-04-08 > 09:49:23+0200) > Maven home: /usr/share/maven > Java version: 1.7.0_19, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19/jre > Default locale: it_IT, platform encoding: UTF-8 > OS name: "linux", version: "3.9.2-200.fc18.i686", arch: "i386", family: "unix" > Reporter: gil cattaneo > > hi > any plan for port jdbc module to hsqldb to latest 2.x series? > i have this problem: > org.apache.openjpa.jdbc.sql.HSQLDictionary.java, the referenced class > is org.hsqldb.Trace. Trace used to contain various error codes, amidst > others VIOLATION_OF_UNIQUE_INDEX . Some of the old error codes in > Trace were ported to the class org.hsqldb.error.ErrorCode in newer > versions of HSQLDB, but VIOLATION_OF_UNIQUE_INDEX is not among them. > any ideas? > thanks in advance for every suggestion -- 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