| From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
|---|---|
| To: | mray(at)360commerce(dot)com |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: extended error codes in the JDBC driver |
| Date: | 2002-05-09 13:52:50 |
| Message-ID: | 1020952370.1383.28.camel@inspiron.cramers |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Matthew,
I will look into this for you. I think it may require work on the
backend to get more meaningful error reporting
Dave
On Wed, 2002-05-08 at 19:08, mray(at)360commerce(dot)com wrote:
>
>
> What would it take to get meaningful extended error code reporting into a more
> useful state? My company is looking at using PostgreSQL for a commercial
> deployment and this seems to be a big roadblock to using PostgreSQL's JDBC
> driver. Is there a company that could be contracted to provide this feature?
> Is this too large a task to do in a relatively short amount of time? Just
> curious since I've been prodded to make a few inquiries on the subject.
>
> Thanks,
> Matthew H. Ray
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2002-05-09 15:42:45 | Re: extended error codes in the JDBC driver |
| Previous Message | senthil kumar | 2002-05-09 06:00:09 | servlet problem |