FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: March 4, 2003 10:53 AM
> 
> 2) I wanted to make a change to implement dbrecftos(). This 
> function will
> open up a file for each new database connection and place in 
> the file the
> contents of the command buffers that are submitted.
>     dbrecftos() takes a single argument - a filename. the 
> filenames it will
> create are then called <filename>.n , where n is an 
> incrementing number from
> zero.
>     If dbrecftos() is called, I was planning to open a new 
> file in each call
> to dbopen(). Trouble is I don't know where to store the file 
> name passed to
> dbrecftos() and the current suffix number, given that I can't 
> store it in the DBPROCESS structure.

I would say add them to DBLIBCONTEXT and use g_dblib_ctx, unless there's an
ODBC or ct-lib equivalent (I didn't find one), in which case use TDSCONTEXT.


Wow.  I just read the ct_debug description for the first time.  If we could
instrument FreeTDS to support that, that would be something.  

I don't know what Sybase's implementation does, but I must say that "name.n"
is pretty informationless.  Does their file include identifying information
at the top?  When the file is opened, I think it would be helpful if you
included:

        date and time
        servername and (client) hostname
        spid
        TDSVER

Perhaps these could be prefixed by "--\t" to mark them as comments amidst
sql text.  

Thanks for the patch, Bill!

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.