Derby
  1. Derby
  2. DERBY-5976

Document the new SQLWarning raised when trying to change the encryption state of an already booted database.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.10.1.1
    • Fix Version/s: 10.10.1.1
    • Component/s: Documentation
    • Labels:
      None
    • Urgency:
      Normal

      Description

      After committing derby-5969-01-aa-warnEncryptionOnBootedDB.diff, we will want to adjust the user guides to clarify the following point:

      o If you are changing the encryption state of the database, be sure to check for SQLWarnings after the change. The change succeeded only if there were no SQLWarnings or SQLExceptions.

      I think that the following sections need to be touched up:

      Developer's Guide:

      o "Encrypting an existing unencrypted database"

      o "Encrypting databases with a new boot password"

      o "Encrypting databases with a new external encryption key"

      o "Decrypting an encrypted database"

      Reference Manual:

      o "dataEncryption=true attribute"

      o "newBootPassword=newPassword attribute"

      o "newEncryptionKey=key attribute"

      o "decryptDatabase=true attribute"

      1. DERBY-5976.zip
        18 kB
        Kim Haase
      2. DERBY-5976.stat
        0.3 kB
        Kim Haase
      3. DERBY-5976.diff
        6 kB
        Kim Haase

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Kim Haase
              Reporter:
              Rick Hillegas
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development