Details
-
Bug
-
Status: Closed
-
Trivial
-
Resolution: Fixed
-
10.10.1.1
-
None
Description
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" ) )
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.)