Skip to Content.
Sympa Menu

freetds - RE: Output parameters (src/dblib/unittests/t0022.c)

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Output parameters (src/dblib/unittests/t0022.c)
  • Date: Tue, 8 Oct 2002 16:51:44 -0400


> From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> Sent: October 8, 2002 4:15 PM
>
> Cool, I forgot about dbtds(). So testing for it is easy.
> But is it the
> right thing to do? I'm concerned that apps expecting the
> TDS4.2 output
> parameter behavior will crash unexpectedly (as t0022.c did
> before I added an
> explicit test to ensure that output parameters were
> received). Is it good
> enough to just document that this doesn't work in TDS7/8, or is there
> something more clever that we should do?

Well, I think of the unittests as testing baseline functionality. They
don't ask FreeTDS to do anything it can't, and they should always succeed
unless we break something.

On that basis, I think t0022.c should test for the TDS version and execute
only if it's < 7.0. Else it should write a warning to stderr indicating
that output parameters are unsupported for such-and-such a version at the
present time, but return success (since the unsupportedness is anticipated).


The nice-guy approach would be to check dbtds() in dbretname() and issue a
client-side error message if the TDS version is out of range. Wouldn't you
say?

Regards,

--jkl


> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> Sent: Tuesday, October 08, 2002 4:05 PM
> To: TDS Development Group
> Subject: [freetds] RE: Output parameters (src/dblib/unittests/t0022.c)
>
>
> > From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> > Sent: October 8, 2002 3:47 PM
> >
> > Is there some way we can limit this test so it
> > doesn't execute for
> > TSD7 and TDS8 connections? Or should we just remove the test
> > altogether?
>
> To test the protocol version being used for a connection, use
> dbtds(). Is
> that what you're looking for?
>
> n.b., The Sybase standard is to use the uppercase equivalent
> macro. <shrug>
>
> --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 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.
>
>
>
> ---
> You are currently subscribed to freetds as:
> [Nicholas_Castellano AT acml.com]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>
>
> 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.
>
>
>
> ---
> You are currently subscribed to freetds as: [LowdenJK AT bernstein.com]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>


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