There is a difference between PostgreSQL and other DBMSs (like MySQL and
Oracle) that makes it difficult to to stabilize ported applications.
When an SQLException occurs, and is caught by the application logic, the
other DBMSs are processing the following SQL commands of the
transaction. This makes sense because the SQLException is caught by the
application logic.
With PostgreSQL all further SQL commands are failing because PostgreSQL
rolls back the current transaction and makes it unusable. That means the
application is crashing although the SQLException ist caught.
The developer has to identify places where this could happen and change
the code. When porting large applications this can be a very difficult.
It would help a lot if PostgreSQL would behave like the other DBMS in
this case.
-- tom
