FreeTDS Development Group

["Eric Deutsch" <edeutsch AT systemsbiology.org>]

> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> 
> Eric, I didn't apply your -d patch for freebcp.  Did you mean to say
it
> *always* logs, regardless of the presence of TDSDUMP?  Or that you'd
like
> to defeat logging for bcp operations?

I meant to say that it *always* logs, the user has no choice.  One of
the first lines in freebcp.c was tdsdump_open(NULL);  I changed it to be
conditional upon the -d flag.  But now that I think about it, maybe we
don't need any of that stuff.  Maybe just setting the TDSDUMP env
variable is the equivalent?  Dunno.  Maybe Bill can chime in with what
the rationale for having the tdsdump_open() explicitly at the beginning
of freebcp.c was.  Maybe it's just left over from the initial writing of
that app.

Thanks,
Eric