You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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).
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
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: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 thedirectory
protocol).Look at http://db.apache.org/derby/docs/10.12/devguide/cdevdvlp40724.html
The text was updated successfully, but these errors were encountered: