Received: from mail.retep.org.uk ([216.126.85.184]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f21LUPx96184 for ; Thu, 1 Mar 2001 16:30:25 -0500 (EST) (envelope-from peter@retep.org.uk) Received: from heather.retep.org.uk ([193.113.114.7]) (authenticated) by mail.retep.org.uk (8.11.1/8.11.1) with ESMTP id f21LUMR96173; Thu, 1 Mar 2001 16:30:22 -0500 (EST) (envelope-from peter@retep.org.uk) Message-Id: <5.0.2.1.0.20010301212711.00a4c030@mail.retep.org.uk> X-Sender: peter@mail.retep.org.uk X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 01 Mar 2001 21:28:36 +0000 To: "David Wall" , From: Peter Mount Subject: Re: JDBC error codes to detect duplicates? In-Reply-To: <02df01c0a282$c352b700$5a2b7ad8@expertrade.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200103/11 X-Sequence-Number: 1172 At 11:06 01/03/01 -0800, David Wall wrote: > > Is there a plan for the JDBC to return the codes for postgres back to >the program? I running 7.1beta4 now. > > > >> AFAIK clean implementation of such feature is not possible because >backend > >> protocol does not have error codes (only error messages) > >Too bad. Is the definitive list of error messages documented? (Probably >yes, but where?) Perhaps we could write an ugly implementation that would >parse the error message and return meaningful errors codes so that all users >don't suffer the same problem. problem is two fold: 1: Enlarges the driver, which affects those who use the driver over a network connection (some people still use JDBC direct in applets) 2: It becomes sensitive to changes during development. An example of #2 is where the Timestamp format changed just slightly, then getTimestamp broke. Peter