Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 5 Oct 2012 01:57:48 +1100 (NCT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1250984253.323.1349362668214.JavaMail.jiratomcat@arcas>
In-Reply-To: <409367018.16174.1338385403126.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (DERBY-5792) Make it possible to turn off
 encryption on an already encrypted database.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan updated DERBY-5792:
-----------------------------------

    Attachment: derby-5792-5a-old_container_removal_cleanup.diff

Attaching patch 5a, which simplifies the method cleaning up the old container files in seg0. I haven't found a reason to keep the two implementations yet (filtering on disk and keeping list in-memory), and this isn't performance critical code.

suites.All passed except for one failure in the compatibility test (10.3), so I'm rerunning tests.

Patch ready for review.
                
> Make it possible to turn off encryption on an already encrypted database.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-5792
>                 URL: https://issues.apache.org/jira/browse/DERBY-5792
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Store
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kristian Waagan
>         Attachments: derby-5792-1a-boilerplate_and_preparation.diff, derby-5792-1b-boilerplate_and_preparation.diff, derby-5792-2a-decryptdatabasetest.diff, derby-5792-3a-decryption_feature.diff, derby-5792-4a-crash_and_dbo.diff, derby-5792-4b-crash_and_dbo.diff, derby-5792-5a-old_container_removal_cleanup.diff
>
>
> Currently, you can encrypt an unencrypted database and you can change the encryption key on an already encrypted database. However, Derby does not expose a way to turn off (unencrypt) an already encrypted database.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira