Sergui,
Actually I think I like this option and all that is really required is
something like
//DEBUG Driver.debug(message)
Then it would compile properly and if you wanted you could enable the
debug statements with a regex of some sort
Dave
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Serguei Mokhov
> Sent: Saturday, March 16, 2002 4:40 PM
> To: Dave@micro-automation.net; pgsql-jdbc@postgresql.org
> Cc: 'Bruce Momjian'
> Subject: Re: [JDBC] JDBC Logging & log4j
>
>
> ----- Original Message -----
> From: "Dave Cramer" <Dave@micro-automation.net>
> Sent: Saturday, March 16, 2002 4:15 PM
>
> > Do we want to put logging in the driver?
> > Why?
> > How much?
> > At what cost?
>
> Needless to say, logging is essential thing to have,
> but to answer the above questions one answer could be - to
> try. If those who care about the logging facilities, could
> simply mirror current dev. tree of the driver, and some in,
> and compare performance between the two on the same set of tests.
>
> Another possible solution just came into my
> not-always-so-smart-head, is to write some pre-processing
> ourselves :). Put some special types of comments in the
> places where the logging seems appropriate like:
>
> //{DEBUG
>
> logSmthHere();
>
> //}DEBUG
>
> Just a simple {PERL, Shell, Python, whatever}-script may run
> through the sources and produce two jars, one compiled with
> DEBUG as it is, the other one will be a stripped out //{DEBUG
> version. Yes, I know this will require some tmp space and
> some extra processing, but could be a solution too.
>
> 2 Canadian cents
>
> -s
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>
>