[
https://issues.apache.org/jira/browse/DERBY-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088700#comment-13088700
]
Knut Anders Hatlen commented on DERBY-5361:
-------------------------------------------
Thanks, the updated topics look good.
One tiny issue... The comment in the REPLACE_JAR example says:
-- SQL statement
-- replace a jar at a remote location
That sounded (to me) like it's the jar at the remote location that is being
replaced by something, whereas it is actually the jar in the database that is
being replaced by the jar at the remote location. Perhaps "replacement jar at a
remote location" would be more accurate?
> Document use of URLs with SQLJ.INSTALL_JAR
> ------------------------------------------
>
> Key: DERBY-5361
> URL: https://issues.apache.org/jira/browse/DERBY-5361
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.8.1.6, 10.9.0.0
>
> Attachments: DERBY-5361-2.diff, DERBY-5361-2.zip, DERBY-5361.diff,
> DERBY-5361.stat, DERBY-5361.zip
>
>
> The reference manual's topic on SQLJ.INSTALL_JAR says the first argument is
> the path of the jar file to add. That argument doesn't have to be a file
> path, it can also be a URL.
> Changes needed:
> - rename JAR_FILE_PATH to JAR_FILE_URL (or perhaps JAR_FILE_PATH_OR_URL?)
> - update description of said parameter to reflect that it can also take a URL
> - add a new example in the SQL examples paragraph:
> -- SQL statement
> -- install jar from remote location
> CALL SQLJ.INSTALL_JAR('http://www.example.com/tours.jar', 'APP.Sample3', 0)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
