[DERBY-4428] Add proper delete mechanism for in-memory databases

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.6.1.0
• Component/s: JDBC, Services, Store
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 29/Oct/09 12:41
• Updated: 29/Apr/10 12:10
• Resolved: 29/Apr/10 12:10

Description

The current mechanism for deleting in-memory databases isn't good enough, and a proper one must be added.
It is also important to be able to delete in-memory databases, since they occupy valuable main memory that should be discarded when the database is no longer needed.

I intend to implement the mechanism by using the JDBC connection URL:
"jdbc:derby:memory:myDatabase;delete=true[;user=X;password=Y]

The connection attempt will throw an exception in any case, either because the request failed or because it succeeded.
Reasons for a failure can be invalid user and/or password, lacking encryption attributes, or conflicting attributes.
For the time being, only the database owner will be allowed to delete databases (note: do we have a way to control/limit in-memory database creation?)

Issue Links

• relates to: DERBY-4432 Memory leak when attempting to boot non-existing database with the in-memory back end
• relates to: DERBY-4590 You can drop a file-system database from a directory named "memory"
• relates to: DERBY-4525 Document the in-memory storage back end

Sub-Tasks

• Refactor existing in-memory back end tests and add new tests for dropping database: Closed