Skip to Content.
Sympa Menu

freetds - Re: coding advice, please...

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: coding advice, please...
  • Date: Tue, 24 Sep 2002 10:31:29 -0400


libtds can't rely on functions in libsybdb. A much, much bigger no-no than
changing return codes.

We really need to be flexible about changing libtds, or we will never get
anywhere. I know it's an exposed API, but it just isn't mature enough at
this point to be set in stone. If people want a reasonably well-defined
API, we provide three of them. Those using the TDS interface have been
warned. How many people are *really* doing this anyway, in production code?

Cheers,
-nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Tuesday, September 24, 2002 10:24 AM
To: TDS Development Group
Subject: [freetds] Re: coding advice, please...



Not pretty but I would put all the tds_process_row_tokens() into dbnextrow
() add
the extra information. Change tds_process_row_tokens() into a wrapper for
dbnextrow() and return the same sucess/fail that people are expecting.
Changing
return codes on people should be a no, no.


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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page