Skip to Content.
Sympa Menu

freetds - RE: [freetds] patch 20031120

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] patch 20031120
  • Date: Thu, 20 Nov 2003 17:01:23 -0500

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafone.com]
> Sent: November 20, 2003 11:29 AM
>
> perhaps this can be a better solution... add a field to
> TDSICONV to store old errors and caller should say if this is
> the first
> and/or the last chunk (in no-chunk conversions it's always
> the first and the last chunk).

This might turn out to be the best answer. In effect, TDSICONV would hold
an "error mask" of messages to suppress. tds_iconv() would add to the mask
as messages accumulated. The problem would be to remember to clear the mask
when done.

tds_iconv.h:
struct _suppress {
unsigned int ei2big:1;
unsigned int eilseq:1;
unsigned int einval:1;
} suppress;
/* ... */

/* caller: */
memset(&iconv_info->suppress, 0, sizeof(iconv_info->suppress));
iconv_info->suppress.eilseq = *wire_size > 0;
irreverisible = tds_iconv(...);

> So you can also reset iconv state (iconv(cd, NULL,
> NULL, NULL, NULL) )... Does this sound reasonable ?

I don't know if this is important. It might be just as easy to call
iconv(3) instead.

--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.






Archive powered by MHonArc 2.6.24.

Top of Page