db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1634) Documented syntax for storing jar files in a db has syntax errors
Date Sat, 26 Aug 2006 01:00:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1634?page=comments#action_12430677 ] 
Stan Bradbury commented on DERBY-1634:

These commands are documented correctly in the Developers Guide.  In addition to the above
problems the qualifiedJarName also needs quotes plus splitting the quoted jarFilePath across
example lines makes if very difficult to read.  Here's the current and corrected text.

Current:   CALL SQL.install_jar('
      ', qualifiedJarName, 0) 
CORRECT:  CALL sqlj.install_jar('jarFilePath', 'qualifiedJarName', 0) 

Current: CALL SQLJ.remove_jar ('
       ', qualifiedJarName, 0)
CORRECT: CALL sqlj.remove_jar( 'qualifiedJarName', 0)

Current:  CALL SQLJ.replace_jar('
            ', qualifiedJarName, 0)
CORRECT: CALL sqlj.replace_jar( 'jarFilePath', 'qualifiedJarName')

> Documented syntax for  storing jar files in a db has syntax errors
> ------------------------------------------------------------------
>                 Key: DERBY-1634
>                 URL: http://issues.apache.org/jira/browse/DERBY-1634
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Priority: Minor
>             Fix For:
> The 'Adding a jar 
> file' section (link below) is missing a J from the "SQL." 
> portion (should be SQLJ).  The 'Removing a jar file' and 
> 'Adding a jar file' sections have 3 parameters in the syntax 
> description and should only have 2 parameters. 
> http://db.apache.org/derby/docs/10.1/tools/ttoolsjarload1002986.html
> http://db.apache.org/derby/docs/10.1/tools/ttoolsjarload1003059.html
> It would also be good to clarify the meaning of the parameters.

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


View raw message