FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

dblib is a "Sybase" API.  We implement Sybase's API in FreeTDS.  I'm not
sure what you mean by "But we are not using any SyBase libraries or
functions at all."  If you are using the DB-Library API, then you are using
libraries and functions whose functionality are defined by Sybase (and also
by Microsoft).

None of this has anything to do with ctlib.  I'm not sure why you mention
ctlib at all.

Actually, the page you quoted says:

"In any other case, this value is considered an error and is treated as an
INT_CANCEL."

So there is a difference in Sybase's specification versus Microsoft's.

Perhaps the FreeTDS behavior should depend on whether or not
"--enable-msdblib" is used at configure time.  Does that sound reasonable?

Cheers,
--nick


-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Wednesday, October 09, 2002 10:40 AM
To: TDS Development Group
Subject: [freetds] RE: Bug found?



(Responding in absense of Mr. Benjaminsson:)

But we are not using any SyBase libraries or functions at all. ctlib is
right out. We are _only_ using the dblib to talk to Microsoft SQL Server
2000. Their documentation, on this page:

http://msdn.microsoft.com/library/en-us/dblibc/dbc_pdc04c_6v39.asp

says _nothing_ of this. Is this perhaps a sign that the ctlib/dblib error
handlers has "to much" in common and should be split up or am I just adding
to the confusion here?


regards,

 Infogate AB             Magnus.Ahl AT infogate.se
 Storgatan 29                   tel: 035-171970
 Box 345                      mobil: 702-118265
 301 08 Halmstad                www.infogate.se

> -----Original Message-----
> From: bounce-freetds-149337 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-149337 AT franklin.oit.unc.edu]On Behalf Of 
> Castellano, Nicholas
> Sent: den 9 oktober 2002 15:55
> To: TDS Development Group
> Subject: [freetds] RE: Bug found?
>
>
> The code that you quote implements the following statement from the 
> Sybase
> dberrhandle() documentation, where it discusses INT_TIMEOUT and
> INT_CONTINUE
> returns from the error handler:
>
> "This return value is meaningful only for timeout errors (SYBETIME).  
> In any other case, this value will be considered an error, and will be 
> treated as an INT_EXIT."
>
> That code, as far as it goes, it correct.
>
> Your error handler should return INT_CANCEL instead.
>
> Additionally, FreeTDS does not yet support the documented behavior for 
> either INT_TIMEOUT or INT_CONTINUE returns in the case of a SYBETIME 
> error. That is a bug (or something we just haven't got around to 
> implementing yet...call it what you will).
>
> Cheers,
> --nick
>
> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> Sent: Wednesday, October 09, 2002 5:12 AM
> To: TDS Development Group
> Subject: [freetds] Bug found?
>
>
> Found the following bug(?) in dbutil.c (revision 1.15).
>
> In the method dblib_handle_err_message:
>
>       if (((rc == INT_TIMEOUT) || (rc == INT_CONTINUE))
>           && (msg->msg_number != SYBETIME)) {
>               rc = INT_EXIT;
>       }
>
> I have registered an own errorhandler that allways
> returns INT_CONTINUE, but it doesn't continue
> when msg->msg_number != SYBETIME.
>
> Should dbutil really ignore that I want to continue?
>
> /Jonas
>
>
>
>
>
>
> ---
> 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: [Magnus.Ahl AT infogate.se] 
> To unsubscribe, forward this message to 
> $subst('Email.Unsub')
>


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