[
https://issues.apache.org/jira/browse/DERBY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032454#comment-13032454
]
Kim Haase commented on DERBY-1780:
----------------------------------
I am moving the information on the SQLJ system procedures from the Tools Guide
to the Reference Manual, where it clearly belongs (see DERBY-5226).
I would be happy to move the conceptual information on using the bulk
export/import system procedures to the Admin Guide, as suggested here. It's
been in the Tools Guide for a long time, however, and people may be used to
finding it there by now. I would appreciate any comments, pro and con, on this
idea.
> 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
> Priority: Minor
>
> 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
