Skip site navigation (1)
Skip section navigation (2)
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.
Peripheral Links
Header And Logo
|
Site Navigation
Porting and Exception handling
- From: tom12167 <tom12167(at)web(dot)de>
- To: pgsql-admin(at)postgresql(dot)org
- Subject: Porting and Exception handling
- Date: Sat, 07 Apr 2007 19:47:41 +0200
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
- Prev by Date: rowcount function in postgres???
- Next by Date: Re: [SQL] rowcount function in postgres???
- Previous by thread: rowcount function in postgres???
- Next by thread: Can't restore a pg_dump due to encoding errors
- Indexes: