From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | Laurette Cisneros <laurette(at)nextbus(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: jdbc 7.2b1 question... |
Date: | 2001-11-14 03:27:04 |
Message-ID: | 3BF1E488.2000705@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Laurette,
This is actually a limitation of the postgresql server itself. The
server currently has no concept of error codes, it only has strings.
Therefore there is little the jdbc driver can do until this
functionality is incorporated into the backend server. This is
currently on the todo list for the server.
thanks,
--Barry
Laurette Cisneros wrote:
> Hi all,
>
> The JDBC API does provide methods to extract data from the SQLException, such as the SQLSTATE and special vendor codes. These usually contains more specific info which allows programmers to make more intelligent choices and recover from errors.
>
> However, the current JDBC code (7.1.3) for postgres seems to be is sorely lacking in the ability to percolate specific errors. Most java sql commands only throw one exception: SQLException. By itself, this doesn't tell us much.
>
> Is there some type of this support in the 7.2 version of the JDBC driver?
>
> Thanks,
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-11-14 04:11:47 | Re: [PATCHES] absolute() error with jdbc7.1-1.2 |
Previous Message | Laurette Cisneros | 2001-11-13 22:30:58 | jdbc 7.2b1 question... |