[
https://issues.apache.org/jira/browse/DERBY-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469219#comment-13469219
]
Knut Anders Hatlen commented on DERBY-5792:
-------------------------------------------
Patch 4b looks fine to me, and it clears up my question about DBO rights. Since
you're planning to fix the messages in a follow-up patch, I'm +1 to both 3a and
4b.
As to the messages, perhaps we could reduce the number of messages needed by
using the same message for encryption, re-encryption and decryption. For
example:
Cannot encrypt, re-encrypt or decrypt a database when there is a global
transaction in the prepared state.
Cannot reconfigure encryption for a read-only database.
...
> 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
>
>
> 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
