db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <dsundst...@gluecode.com>
Subject Re: multiple systems in same VM?
Date Thu, 07 Oct 2004 16:20:51 GMT
On Oct 7, 2004, at 9:05 AM, Daniel John Debrunner wrote:

> Hash: SHA1
> Khin, Gerald wrote:
>>> -----Original Message-----
>>> From: Daniel John Debrunner [mailto:djd@debrunners.com]
>>> (snip)
>>> I'm not sure I understand what you mean by multiple systems.
>>> Can you give examples of the benefits of this? E.g. if app1
>>> is using db1 and
>>> app2 is using db2 then what would be gained with two Derby
>>> systems over the single one that is supported today?
>> For example if app1 relies on that the derby.system.home points to
>> location1 and app2 wants derby.system.home to be set to location2.
> It's an interesting idea, would require that every connection request
> through DriverManager include an attribute that indicates which system
> should be used. For a DataSource the system identifier could be a 
> property.
> An alternate approach is to not rely on system functionality or system
> properties. Make the database self-contained, store properties within
> the database. This works today.

Wow great news.  Is there a way I can turn that back on?


View raw message