pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: tom12167 <tom12167@web.de>
To: pgsql-admin@postgresql.org
Subject: Porting and Exception handling
Date: Sat, 07 Apr 2007 19:47:41 +0200
Message-ID: <4617D93D.7090901@web.de> (raw)

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



Message-ID: <4617D93D.7090901@web.de>
Permalink:  ../4617D93D.7090901@web.de/
Also on:    postgresql.org/message-id/4617D93D.7090901@web.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tom12167@web.de
  Subject: Re: Porting and Exception handling
  In-Reply-To: <4617D93D.7090901@web.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox