db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laura Stewart (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1721) DOCS - Retitle topics with duplicate titles in Dev Guide re: Encryption
Date Fri, 18 Aug 2006 00:24:13 GMT
DOCS - Retitle topics with duplicate titles in Dev Guide re: Encryption
-----------------------------------------------------------------------

                 Key: DERBY-1721
                 URL: http://issues.apache.org/jira/browse/DERBY-1721
             Project: Derby
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 10.2.0.0, 10.2.2.0, 10.3.0.0
            Reporter: Laura Stewart
            Priority: Minor


In the Developers Guide. there are 2 sections that contain information about encryption. 
In some cases there are topics with different content but with the same titles. 
There should not be duplicate titles in the Derby documentation.

There is this section: 
JDBC applications and Derby basics -->Derby embedded basics -->Working with the database
connection URL attributes 
that has these topic titles: 
--Using the databaseName attribute 
--Shutting down Derby or an individual database 
--Creating and accessing a database 
--Providing a user name and password 
--Encrypting a database when you create it 
--Booting an encrypted database 
--Specifying attributes in a properties object 

Then there is this section: 
Derby and Security -->Encrypting databases on disk -->Working with encryption 
that has these topic titles: 
--Encrypting databases on creation 
--Creating the boot password 
   --Specifying an alternate encryption provider 
   --Specifying an alternate encryption algorithm 
--Booting an encrypted database 
--Changing the boot password 

Someone needs to look at the content of these files, rework the information and necessary,
create the related links, and then retitle the topics to avoid duplicate titles.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message