Skip to Content.
Sympa Menu

freetds - RE: [freetds] new Ct-library patch

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] new Ct-library patch
  • Date: Tue, 4 Mar 2003 17:58:56 +0100

>
> Hi all,
>

Hi Bill!

> I have posted my patch for the ct-library enhancements on sourceforge.
> I hope I've made everything as easy as poosible to allow the
> patch to be
> applied.
>
> I have a couple of other things...
>
> 1) I sent a patch for dblibrary to the mailing list a while
> ago (17th Feb).
> I know you all have been busy :-) but I wanted to make
> sure that the
> patch hadn't been lost.
> It got sort of "held up" in the mailing list because of
> it's size. Would
> it be useful to post it to sourceforge ?
>

I applied your patch now (I supposed James applied it...)
I don't like some implementation... more to come...

> 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.
> Would global variables in dblib.c be acceptable, or might there be
> threading issues with global variables ?
>
> regards,
>

I'm unable to apply ctlib-patch after applying dblib patch (query.c fail)
Can you post an updated patch?

freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================




Archive powered by MHonArc 2.6.24.

Top of Page