Ahh, you're right, of course.

Actually, I was thinking of starting the task of wrapping all the logging
statements with the appropriate isLoggingDebug() [or whatever] tests. I
believe that someone once noted on this list that those test were almost
universally missing.

I was also wondering it might be appropriate to use the Jakarta Commons
Logging package to introduce an abstraction layer between the driver and the
actual logging mechanism (eg, Log4J, or the host application's native
logging facility). I think this would be a very developer-friendly thing to
do. It would certainly play more nicely with my own application.

http://jakarta.apache.org/commons/logging.html

Any thoughts? I have some cycles available and would be willing to lead the
charge on this. (I'd also like to take a stab at tweaking the exception
architecture to give better diagnostics, to help alleviate the pain many of
us have felt debugging configuration problems).

.T.

On 7/18/02 2:47 AM, rrokytskyy@... wrote:

> Hi,
>
> Unfortunatelly setting the priority to ERROR will not solve the
> problem. Driver will still generate tons of log messages, they will
> simply not appear in log. This is very expensive in terms of CPU and
> memory, so you'd better switch logging off (it should be off by
> default, but you can force it with -DFBLog4j=false). Any error
> condition will result in SQLException, so you can be sure that you do
> not miss anything.
>
> Roman.

--
Every great movement must experience three stages: ridicule, discussion,
adoption. -- John Stuart Mill