From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Fixing SQLException error codes. |
Date: | 2001-06-25 15:42:24 |
Message-ID: | 3B375BE0.3030005@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Barry Lind wrote:
> No, the backend does not have proper error codes. See the TODO list
> item "Allow elog() to return error codes, module name, file name, line
> number, not just messages (Peter E) [elog]"
> (http://www.postgresql.org/docs/todo.html)
>
> It doesn't make sense to do this in JDBC until the server first supports
> error codes. If you want to contribute, it would be best to help
> getting this into the core server so that all interfaces, not just JDBC
> can take advantage of it.
>
> thanks,
> --Barry
>
> PS. I agree this would be nice to have in core as well as JDBC.
>
>
> Martin Algesten wrote:
>
>> Well yeah... that is the question.. Does the backend have standardised
>> error
>> codes... I hoped someone could point me in the right direction before
>> I do
>> anything that isn't useful in the long run.
>>
>> M
>>
>> On 24/6/01 11:16, "Joe Shevland" <J(dot)Shevland(at)eclipsegroup(dot)com(dot)au> wrote:
>>
>>
>>> 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(at)taglab(dot)com]
>>>> Sent: Sunday, 24 June 2001 7:41 PM
>>>> To: pgsql-jdbc(at)postgresql(dot)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(at)postgresql(dot)org
>>>>
>>>>
>>> ---------------------------(end of broadcast)---------------------------
>>> TIP 2: you can get off all lists at once with the unregister command
>>> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>>>
>>>
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 3: if posting/reading through Usenet, please send an appropriate
>> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>> message can get through to the mailing list cleanly
>>
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-06-25 15:42:47 | Re: [HACKERS] Instrumenting and Logging in JDBC |
Previous Message | Barry Lind | 2001-06-25 15:41:52 | Re: [ADMIN] High memory usage [PATCH] |