You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by ch...@apache.org on 2013/08/27 15:22:51 UTC
svn commit: r1517811 - in /db/derby/docs/branches/10.10/src/devguide:
cdevspecial41728.dita cdevspecial53165.dita
Author: chaase3
Date: Tue Aug 27 13:22:51 2013
New Revision: 1517811
URL: http://svn.apache.org/r1517811
Log:
DERBY-6316 Small typos in devguide examples
Merged patch DERBY-6316.diff to 10.10 doc branch from trunk revision 1517808.
Modified:
db/derby/docs/branches/10.10/src/devguide/cdevspecial41728.dita
db/derby/docs/branches/10.10/src/devguide/cdevspecial53165.dita
Modified: db/derby/docs/branches/10.10/src/devguide/cdevspecial41728.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.10/src/devguide/cdevspecial41728.dita?rev=1517811&r1=1517810&r2=1517811&view=diff
==============================================================================
--- db/derby/docs/branches/10.10/src/devguide/cdevspecial41728.dita (original)
+++ db/derby/docs/branches/10.10/src/devguide/cdevspecial41728.dita Tue Aug 27 13:22:51 2013
@@ -60,12 +60,14 @@ as follows:</p>
<codeblock>try {
preparedStatement.execute();
} catch (SQLException se ) {
- String SQLState = se.getSQLState();
- if ( SQLState.equals( "23505" ) )
- { correctDuplicateKey(); }
- else if ( SQLState.equals( "22003" ) ) {
- correctArithmeticOverflow(); }
- else { throw se; }
+ String SQLState = se.getSQLState();
+ if ( SQLState.equals( "23505" ) ) {
+ correctDuplicateKey();
+ } else if ( SQLState.equals( "22003" ) ) {
+ correctArithmeticOverflow();
+ } else {
+ throw se;
+ }
}</codeblock>
<p>Of course, users also have the choice of not wrapping SQL statements in
try-catch blocks within methods. In that case, <i>SQLExceptions</i> are caught
Modified: db/derby/docs/branches/10.10/src/devguide/cdevspecial53165.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.10/src/devguide/cdevspecial53165.dita?rev=1517811&r1=1517810&r2=1517811&view=diff
==============================================================================
--- db/derby/docs/branches/10.10/src/devguide/cdevspecial53165.dita (original)
+++ db/derby/docs/branches/10.10/src/devguide/cdevspecial53165.dita Tue Aug 27 13:22:51 2013
@@ -28,13 +28,15 @@ limitations under the License.
</metadata></prolog>
<conbody>
<p>For example:</p>
-<codeblock>CREATE TRIGGER . . .
-DELETE FROM flightavailability
- WHERE flight_id IN (SELECT flight_id FROM flightavailability
- WHERE YEAR(flight_date) < 2005);) </codeblock>
+<codeblock><b>CREATE TRIGGER . . .
+DELETE FROM FlightAvailability
+ WHERE flight_id IN (SELECT flight_id FROM FlightAvailability
+ WHERE YEAR(flight_date) < 2005);</b>
+</codeblock>
<p>A trigger action does have some limitations, though; for example, it cannot
contain dynamic parameters or alter the table on which the trigger is defined.
-See "TriggerAction" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
+See the "Triggered-SQL-statement" section of the "CREATE TRIGGER statement"
+topic in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
details. </p>
</conbody>
</concept>