db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4428) Add proper delete mechanism for in-memory databases
Date Thu, 29 Oct 2009 12:41:59 GMT
Add proper delete mechanism for in-memory databases
---------------------------------------------------

                 Key: DERBY-4428
                 URL: https://issues.apache.org/jira/browse/DERBY-4428
             Project: Derby
          Issue Type: Improvement
          Components: JDBC, Services, Store
    Affects Versions: 10.6.0.0
            Reporter: Kristian Waagan
            Assignee: Kristian Waagan


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?)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message