I've had exactly the same problem which has to do with Eclipse not being
aware of embedded Derby specific way to shutdown. Eclipse only closes
connection and database stays open. I solved this by running standalone
Derby network server and connecting from Eclipse and application as network
client.
For some reasons I'm using derby embedded driver.
The application performs as expected unless, for debug purpose, I open
the database from eclipse DatabaseDevelopment perspective.
Even if i close the connection from DatabaseDevelopment and closing
DatabaseDevelopment perspective too, when I
Il 30.10.2015 11.41, Peter Ondruška ha scritto:
I've had exactly the same problem which has to do with Eclipse not
being aware of embedded Derby specific way to shutdown. Eclipse only
closes connection and database stays open. I solved this by running
standalone Derby network server and
