Excellent news! Thanks for digging down to uncover the source of the
problem, and thanks for sharing your discoveries with us.
I know very little about pax-jdbc, but it seems like useful software; it
would be nice if it cleanly supported both the Embedded and Client-Server
driver configurations
> 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
On Sat, Aug 12, 2017 at 9:47 AM, Steinar Bang wrote:
>
> Ok, I interpret this answer to be that there shouldn't be any problems
> with pulling the embedded driver and the client driver into the same
> java program?
>
>
>
Yes, that's my belief.
You might experience higher-level
> 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
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 packages, making it easy to have
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