This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 121703 - Set "derby.system.home" property for the embedded Derby databases
Summary: Set "derby.system.home" property for the embedded Derby databases
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Libor Fischmeistr
Depends on:
Reported: 2007-11-12 09:03 UTC by ndario
Modified: 2013-08-01 12:52 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description ndario 2007-11-12 09:03:09 UTC
JavaDB settings currently allow setting "derby.system.home" property only for the network server. There is no option to
set "derby.system.home" property within the IDE to use with embedded driver.
Workaround is to set "derby.system.home" property as a startup parameter for NB with "-J-D", but changing it requires
IDE restart.
Would solution be to call 
System.setProperty("derby.system.home","value from the textfield");
once the OK button in settings dialog is clicked?
Comment 1 David Vancouvering 2007-11-12 16:50:12 UTC
Thanks, ndario.  I was thinking about this further and although this is a good idea, we'd need to test.  Note that if
you set derby.system.home for the NB VM, then every project with its own classloader will want to access the same
database when using an embedded connection.  But Java DB only allows one classloader at a time to access a database
through an embedded connection.  So this requires further thought...

I'm not sure about this being a P1 feature, but I'll leave it for now.
Comment 2 ndario 2007-11-12 20:22:14 UTC
Ups, sorry about P1, I thought it is the "least important". Feel free to set priority as you like, I set it to P1 by
Comment 3 Jiri Rechtacek 2009-10-16 14:09:55 UTC
Reassigned to new owner.