Re: Crystal Reports / PostgreSQL - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Crystal Reports / PostgreSQL
Date
Msg-id 420BCD50.1000608@opencloud.com
Whole thread Raw
In response to Re: Crystal Reports / PostgreSQL  (Kris Jurka <books@ejurka.com>)
Responses stack traces are evil (was: Re: Crystal Reports / PostgreSQL)  (Vadim Nasardinov <vadimn@redhat.com>)
List pgsql-jdbc
Kris Jurka wrote:
>
> On Thu, 10 Feb 2005, Vadim Nasardinov wrote:
>
>
>>Out of curiousity though, what makes it error-prone?
>>
>
>
> Any ad-hoc parsing is easy to get wrong by forgetting corner cases.  I'm
> not saying it can't be done correctly, just that we shouldn't bother.

Especially given that different JVMs format stack traces differently,
and Throwable.getStackTrace() is allowed to omit stack frames.

I think setting a DriverManager log writer is the simplest solution
here, closely followed by making notImplemented() take a method name arg.

-O

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Crystal Reports / PostgreSQL
Next
From: "Xavier Poinsard"
Date:
Subject: Patch adding name for NotImplemented