If a tool like ij is started in a new JVM, then it will not be able to connect to an embedded database which has been started by a different JVM.
On 9/10/07, Néstor Boscán <email@example.com> wrote:
Thanks for the answer.
So this means that if I open the database using the EmbeddedDriver driver no
one can access the database from an outside connection?. Includiing tools
Enviado el: Monday, September 10, 2007 4:27 AM
Para: Derby Discussion
Asunto: Re: How to restrict external connections
Néstor Boscán wrote:
> Is there a way to restrict external connection to a Derby Database?. I
> only want the JVM to be able to connect to the Derby database and no
> other external processes.
Unless I have misunderstood, sounds like you simply want to use Derby
embedded. This is done by using org.apache.derby.jdbc.EmbeddedDriver and
specifying the connection URL as 'jdbc:derby:myDatabase[;create=true;...]'.
By default, no network server will be started and only the JVM is able to
access the database.
Note that 'myDatabase' can point to a database by using either a relative
path (relative to derby.system.home
, or current working directory if it is
unset) or an absolute path.
Did that answer you question, or do you have any further requirements?
> Néstor Boscán