db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Harrigan <dharri...@gmail.com>
Subject Re: Setting the derby.system.home in the url
Date Wed, 28 Mar 2007 16:47:07 GMT


Understand, but that doesn't answer why properties such as logDevice etc...
are allowed to be passed in on every url connection. It would be nice that
*if* set from the url it uses that in the static field, otherwise it
defaults to whatever
value is presently there. It would make development easier. No?


John Embretsen wrote:
> David Harrigan wrote:
>> Hi,
>> Is there any technical reason why it can't be possible to do this?
>> jdbc:derby:media;systemHome=/tmp
>> which would be used as the derby.system.home. I notice there are other
>> similar values, e.g., logging...
>> It would make development nicer when using JPA, so I can just pass in
>> this
>> rather than having to put a -Dderby.system.home in my jvm...
>> Anyone like to offer up a comment?
> Well, my hunch is that you cannot do this because derby.system.home is a
> static,
> system-wide property. Only the URL used for booting the Derby system can
> be
> allowed to set the system home this way, if support for this had been
> implemented. Subsequent connection attempts using the same URL would
> either have
> to return with an error (exception) or silently ignore the "systemHome"
> attribute.
> -- 
> John

View this message in context: http://www.nabble.com/Setting-the-derby.system.home-in-the-url-tf3480771.html#a9717752
Sent from the Apache Derby Users mailing list archive at Nabble.com.

View raw message