Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1139784740.1259239779709.JavaMail.jira@brutus>
Date: Thu, 26 Nov 2009 12:49:39 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4428) Add proper delete mechanism for
 in-memory databases
In-Reply-To: <1489278540.1256820119353.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4428:
-----------------------------------

    Issue & fix info:   (was: [Patch Available])
       Fix Version/s: 10.6.0.0

> 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
>             Fix For: 10.6.0.0
>
>         Attachments: derby-4428-0a-preview_patch.diff, derby-4428-1a-in_memory_specific_delete_code.diff, derby-4428-1a-in_memory_specific_delete_code.stat, derby-4428-1b-in_memory_specific_delete_code.diff, derby-4428-2a-generic_db_drop.diff, derby-4428-2b-generic_db_drop.diff, derby-4428-3a-canonical_name_handling.diff, derby-4428-3b-canonical_name_handling.diff
>
>
> 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.