[ 
https://issues.apache.org/jira/browse/DERBY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041742#comment-13041742
 ] 

Kim Haase commented on DERBY-1780:
----------------------------------

Committed patch DERBY-1780-2.diff to documentation trunk at revision 1129834. 
Merged to 10.8 doc branch at revision 1129837.

This is patch 2 of 3, which removes the old topics from the Tools Guide.


> Document all supplied system procedures in the Server and Administration 
> Guide (e.g. class loading utils and import/export)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1780
>                 URL: https://issues.apache.org/jira/browse/DERBY-1780
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.0.2.1, 10.1.2.1, 10.1.3.1
>            Reporter: Stan Bradbury
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-1780-1.diff, DERBY-1780-1.stat, DERBY-1780-1.zip, 
> DERBY-1780-2.diff, DERBY-1780-2.stat, DERBY-1780-2.zip, DERBY-1780-3.diff, 
> DERBY-1780-3.stat, DERBY-1780-3.zip
>
>
>  Most of the utilities cataloged in SYSCS_UTIL are used to setup/initialize a 
> Derby system and are invoked using an existing connection using the 'CALL' 
> command,  Such topics are best covered in the the Server and Administration 
> Guide. Currently the procedures install_jarfiles, replace_jarfiles, 
> remove_jarfiles, SYSCS_IMPORT_TABLE / DATA and SYSCS_EXPORT_TABLE / QUERY are 
> documented in the Tools and Utilities Guide.  
> I recommend reserving the Tools and Utilities Guide for routines that have a 
> standalone interface (e.g. an existing connection is not required to invoke 
> the routine), currently that is IJ, sysinfo and dblook.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to