Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Derby database: protocol - support using existing database #15

Open
bindul opened this issue Jan 18, 2016 · 0 comments
Open

Derby database: protocol - support using existing database #15

bindul opened this issue Jan 18, 2016 · 0 comments

Comments

@bindul
Copy link
Contributor

bindul commented Jan 18, 2016

Preamble

Right now, the EmbeddedDerbyResource starts Derby with ;create=true option. This fails if the directory exists (irrespective of if it is a database directory) with error:

Caused by: ERROR XBM0J: Directory /some/dir/path already exists.

Derby seems to like to create its own directory for the database (separate issue where the error message from Derby is misleading with the database name).

Feature

The feature to implement is to support starting a database from an existing database directory (without ;create=true on the directory protocol).

Look at http://db.apache.org/derby/docs/10.12/devguide/cdevdvlp40724.html

@bindul bindul added this to the v1.0-alpha.1 milestone Jan 18, 2016
bindul added a commit that referenced this issue Feb 19, 2016
Added support to skip the create=true attribute in the JDBC URL to
initialize the database.
Fixed / Cleaned up tests and documentation

Resolves #15

Change-Id: Id8bd785c102868a1cd6b27bf284572b1cf5a121b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Derby Junit Helper
Done on Feature Branch
Development

No branches or pull requests

1 participant