[
https://issues.apache.org/jira/browse/CONNECTORS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041339#comment-13041339
]
Karl Wright commented on CONNECTORS-114:
----------------------------------------
Just got email from the HSQLDB team, and confirmed that the deadlock issue was
resolved in hsqldb 2.2.2. So it looks like we have a third database that
ManifoldCF can work with. I've checked in the updated database jar, and am
planning on writing a test series that uses hsqldb, much like the series that
uses PostgreSQL.
We've still got to settle on how precisely to do the equivalent of PostgreSQL's
DISTINCT ON functionality, but that's all that is left. Also, FWIW, HSQLDB
doesn't (as yet) seem to fail so spectacularly dealing with hopcounts as Derby
does.
> Derby seems too unstable in multithreaded situations to be a good database
> for ManifoldCF, so try to add support for HSQLDB
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-114
> URL: https://issues.apache.org/jira/browse/CONNECTORS-114
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Reporter: Karl Wright
>
> Derby seems to have multiple problems:
> (1) It has internal deadlocks, which even if caught cause poor performance
> due to stalling (CONNECTORS-111);
> (2) It has no support for certain SQL constructs (CONNECTORS-109 and
> CONNECTORS-110);
> (3) It locks up entirely for some people (CONNECTORS-100).
> HSQLDB has been recommended as another potential embedded database that might
> work better.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
