[unixODBC-support] driver logging

Eric Sharkey sharkey at netrics.com
Tue Mar 1 17:10:49 GMT 2005


The template driver distributed with unixODBC integrates facilities
for logging information from within the driver, but there doesn't
really seem to be any way to control this functionality.  The logical
thing would be to have the driver respond to SQL_ATTR_TRACE, and
SQL_ATTR_TRACEFILE connection attributes, but the DM intercepts these
calls and never passes them on to the driver.  Do you guys have any
thoughts on this?

What is the advantage of storing log messages in memory?  The
template keeps up to 50 messages in RAM per handle and never seems
to do anything with them.  Is there a point to this?  Just to
have them there if you attach a debugger?

Why do the log facilities require a sprintf to an external buffer
prior to logPushMsg?  Isn't it better to have logPushMsg take
a variable argument list and call vsnprintf/vfprintf rather than
strdup/fprintf?

Eric



More information about the unixODBC-support mailing list