Thank you Rick and All, all clear now.
The app can be taken down. I just trying to wrap my head around this scenario,
since I am not great in Derby and doc is bit scant for this case.
Ok, so I see the connection via network drive is an option. Does Derby exposes
the any listening port when it is started in embedded mode?
> On Aug
No, that is not supported using the embedded driver only.
You either have to shut down the application, or connect using the network
driver (while the application itself connects using the embedded driver).
The "embedded server mode" is described at [1] and in the admin guide.
Do you need the
Thanks you Kristian,
Booting/opening is clear. But say Derby is booted/opened by an application, can
I connect to the same database via IJ tools and interface with the database
(UPDATE/INSERT/DELETE)? Or this is not supported?
> On Aug 2, 2017, at 10:39 AM, Kristian Waagan
Hi Dmitry,
Only one process can open / boot a specific database (usually a set of
files on disk) at a given time.
Depending on your requirements you can:
a) shut down the application and boot the database using any standard JDBC
tool (using the embedded driver)
b) if you need to be able to
Hi List!
I have a tough problem: My application runs Derby in embedded mode and I have a
requirement to change/correct data inside this database.
What is a best way to do this if it is possible? For example if I open this
database location via "file://patch to db folder” will this work properly
