Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 3369E9FB58E for ; Sat, 7 Apr 2007 14:49:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 46952-02 for ; Sat, 7 Apr 2007 14:49:19 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id D776F9FB295 for ; Sat, 7 Apr 2007 14:49:19 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from h57078.serverkompetenz.net (talk-net.net [81.169.128.8]) by svr4.postgresql.org (Postfix) with ESMTP id 2C2D35AF888 for ; Sat, 7 Apr 2007 17:49:19 +0000 (GMT) Received: from [192.168.115.250] (e178159011.adsl.alicedsl.de [85.178.159.11]) by h57078.serverkompetenz.net (Postfix) with ESMTP id 7D47B50C9AA for ; Sat, 7 Apr 2007 19:36:06 +0200 (CEST) Message-ID: <4617D93D.7090901@web.de> Date: Sat, 07 Apr 2007 19:47:41 +0200 From: tom12167 User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Porting and Exception handling Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.136 tagged_above=0 required=5 tests=BAYES_50=0.001, FORGED_RCVD_HELO=0.135 X-Spam-Level: X-Archive-Number: 200704/64 X-Sequence-Number: 25128 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