RE: Fixing SQLException error codes.
От | Joe Shevland |
---|---|
Тема | RE: Fixing SQLException error codes. |
Дата | |
Msg-id | C56487636E5CD4119B1E00D0B789098ADA2BFD@MEL-EXCH1 обсуждение исходный текст |
Ответ на | Fixing SQLException error codes. (Martin Algesten <martin@taglab.com>) |
Ответы |
Re: Fixing SQLException error codes.
|
Список | pgsql-jdbc |
This would be a very handy feature, Oracle's JDBC implementation does this and it makes it nice and easy to produce descriptive error messages for the end user (among other things). I'm wondering if there are standard error codes returned by the backend or whether you need to create new ones. I can't see there being any problem with it though. I've got a few links to the Oracle JDBC error codes if you want a reference. Regards, Joe > -----Original Message----- > From: Martin Algesten [mailto:martin@taglab.com] > Sent: Sunday, 24 June 2001 7:41 PM > To: pgsql-jdbc@postgresql.org > Subject: [JDBC] Fixing SQLException error codes. > > > Hi all! > > I would like to have the problem with the getErrorCode in SQLException > always returning 0 fixed. So I figured, why don't do it > myself? ... Just tot > check before I start looking at it... > > Has there been any attempt fixing it? Are someone doing it > anyway? Are there > any known problems with doing it? > > Cheers, > Martin > > > ---------------------------(end of > broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to > majordomo@postgresql.org >
В списке pgsql-jdbc по дате отправления: