>>>>> Jerry Lampi <[email protected]>: > I have used Derby for years and have yet to have any problems with it. I > employ a good range of SQL capabilities, but try to avoid (what I would > consider) excessive complexity. Derby is good and valuable software and I > thank you profusely for it!
I have had one issue with derby and that has been when using liquibase to set up schemas in memory databases a pax exam OSGi integration test. The lifecycle of objects in pax exam tests is... kinda weird. But it used to work up to a certain point. Now it works in some apps and not in others and sometimes spottily, even though the java code is basically the same for all of the tests. Only the schemas differ. Since the version of derby I'm using is the one used by pax-jdbc (10.14.2.0) and there didn't seem to be much development going on in derby I switched to file based h2 on the integration test of my liquibase-karaf-feature https://github.com/steinarb/liquibase-karaf-feature/blob/master/liquibase-integration-test/karaf.liquibase.sample/src/main/feature/feature.xml#L19
