Changes between Version 15 and Version 16 of TracDev/Exceptions

Timestamp:

Feb 23, 2016, 9:37:13 PM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracDev/Exceptions

@@ +1 @@
+[[PageOutline(2-3,Contents)]]
+
 = Exceptions
 
+In programming '''exceptions''' are conditions of the program that require special processing. Handling exceptions is important, because to the user the program should function as if it were in a normal state whereby any exceptions that are encountered are handled in the background. See also [wikipedia:Exception_handling].
+
+This page lists the most common exceptions in Trac core and database communication.
+
 == Custom Trac Exceptions
+
 Trac defines a set of custom exception types:
 
@@ -61 +68 @@
 But changing the existing hierarchy might be difficult without breaking backward compatibility.
 
-== DB Exceptions
-We can catch [pep:0249#exceptions Python DB API exceptions] in a DB-neutral way. (Since Trac 1.0, see #6348.)
+== Database Exceptions
+
+We can catch [pep:0249#exceptions Python DB API exceptions] in a database neutral way. (Since Trac 1.0, see #6348.)
 {{{#!python
 try: 
@@ -70 +78 @@
     ... 
 }}}
+
 The above example catches `sqlite.IntegrityError`, `MySQLdb.IntegrityError` or `psycopg.IntegrityError`, 
 depending on the selected DatabaseBackend.
 
-
 ----
 See [query:keywords~=exception tickets]