db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5226) SQLJ system procedures should be documented in Reference Manual
Date Mon, 16 May 2011 20:12:47 GMT

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

Rick Hillegas commented on DERBY-5226:

Hi Kim,

These changes look good to me. Here are some answers to the questions you posed:

For more information on the SQLJ procedures, the following summary by Andrew Eisenberg is
useful: www.sigmod.org/publications/sigmod-record/9912/standards.pdf.gz


I think that 32672 is ok as the length of the String arguments to install_jar.

As you noted, Derby does not use the trailing deploy argument. According to the SQLJ documentation,
if that argument is set to 1, it tells the database to look inside the jar file for an SQL
script (a deployment descriptor) and run that script when the jar file is put into the database.
The script registers the routines and types defined in the jar file and grants access to them.


I think that the unused trailing undeploy argument, if set to 1, indicates that the jar file
contains a de-registration script which should be run when the jar file is removed. The summary
document above doesn't discuss this in detail.

> SQLJ system procedures should be documented in Reference Manual
> ---------------------------------------------------------------
>                 Key: DERBY-5226
>                 URL: https://issues.apache.org/jira/browse/DERBY-5226
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-5226.diff, DERBY-5226.stat, DERBY-5226.zip
> The system procedures SQLJ.INSTALL_JAR, SQLJ.REMOVE_JAR, and SQLJ.REPLACE_JAR are currently
documented in the Tools and Utilities Guide (and briefly referenced in the Developer's Guide).
This reference material should be moved to the system procedures section of the Reference
Manual and revised to be consistent in style with the other topics in that section.
> DERBY-1780 mentions this situation, as do comments on DERBY-484.
> This issue should be fixed before DERBY-484 so that the new topic can link correctly
to the new reference topics.

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

View raw message