In my project[1] I am using a derby in-memory database with the embedded
driver for unit testing and integration testing. I am using PostgreSQL
as the production server.
I am using Liquibase[2] to set up the schema for both Derby and
PostgreSQL, and I'm also using Liquibase to set up the test dat
> Bryan Pendleton :
> I suspect your problems are caused by having two different versions of
> the Derby jars intermingled. The behavior of CLASSPATH is complex,
> especially for things like the JDBC 4.0 autoload features, and Derby
> jars are often packaged and bundled into other software pac
> Bryan Pendleton :
> Anyway, yes, please try to figure out if you have any CLASSPATH conflicts,
> and please do let us know the results of your investigations!
The reason for my problems turned out to be quite simple.
I'm using the pax-jdbc DerbyDataSourceFactory in my derby database
bundle
I needed to temporarily run a derby network server to examine behaviour
of some of my SQL queries, that was different in derby (which I use for
tests, both unit tests and integration tests), and PostgreSQL.
What I did, was to create a maven project that uses the
derby-maven-plugin[1] to start and
I use PostgreSQL as my production database, and I use derby during
development and testing.
I use liquibase to configure and populate the databases:
1. I have a library jar that sets up a database schema using liquibase
https://github.com/steinarb/ukelonn/blob/master/ukelonn.db.liquibase/sr
