[ 
https://issues.apache.org/jira/browse/DERBY-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim Haase resolved DERBY-6316.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
                      10.10.1.3
    Issue & fix info:   (was: Patch Available)

Thanks, Knut! Might as well commit to trunk and branch both --

Committed patch DERBY-6316.diff to documentation trunk at revision 1517808. 
Merged to 10.10 doc branch at revision 1517811.
                
> Small typos in devguide examples
> --------------------------------
>
>                 Key: DERBY-6316
>                 URL: https://issues.apache.org/jira/browse/DERBY-6316
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.10.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>            Priority: Trivial
>             Fix For: 10.10.1.3, 10.11.0.0
>
>         Attachments: DERBY-6316.diff, DERBY-6316.stat, DERBY-6316.zip
>
>
> I came across two examples with small typos in the developer's guide.
> http://db.apache.org/derby/docs/10.10/devguide/cdevspecial41728.html:
> try {
>     preparedStatement.execute();
> } catch (SQLException se ) {
>         String SQLState = se.getSQLState();
>     if ( SQLState.equals( "23505" ) ) 
>         { correctDuplicateKey(); }
>     else if ( SQLState.equals( "22003" ) ) {    
>         correctArithmeticOverflow(); }
>     else { throw se; }
> }
> Here, the first line in the catch block is not at the same indentation level 
> as the other statements in the block.
> http://db.apache.org/derby/docs/10.10/devguide/cdevspecial53165.html:
> CREATE TRIGGER . . .
> DELETE FROM flightavailability 
>       WHERE flight_id IN (SELECT flight_id FROM flightavailability 
>               WHERE YEAR(flight_date) < 2005);) 
> This example has an unmatched closing parenthesis. And even if it were 
> matched, it should have come before the semicolon.
> (By the way, should the semicolon be kept or removed? Derby's SQL dialect 
> doesn't accept statements that end with a semicolon, but ij does.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to