X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 58526DAF74 for ; Wed, 26 Oct 2005 17:30:54 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 81091-04 for ; Wed, 26 Oct 2005 20:30:48 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by svr1.postgresql.org (Postfix) with ESMTP id D2B95DAE64 for ; Wed, 26 Oct 2005 17:30:48 -0300 (ADT) Received: from p54AD285E.dip0.t-ipconnect.de [84.173.40.94] (helo=[192.168.1.10]) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKwh2-1EUrv54BuG-0007BM; Wed, 26 Oct 2005 22:30:47 +0200 Message-ID: <435FE776.7030402@online.de> Date: Wed, 26 Oct 2005 22:30:46 +0200 From: Christoph Zwerschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041206 Thunderbird/1.0 Mnenhy/0.6.0.104 X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Re: Interpreting PostgreSQL error messages References: <435E97CD.9000602@online.de> <1287.1130297661@sss.pgh.pa.us> In-Reply-To: <1287.1130297661@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:d4c19f41f9a9703255691874c1441822 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 required=5 tests=[none] X-Spam-Level: X-Archive-Number: 200510/29 X-Sequence-Number: 5791 The future enhancements sound good. That's definitely something that will be very useful, and yes, interfaces should provide new functionality as soon as possible. But what is the best way to solve the mentioned problem right now? -- Christoph