Skip to Content.
Sympa Menu

freetds - Re: dberrhandler() and dbmsghandler()

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: dberrhandler() and dbmsghandler()
  • Date: Fri, 6 Sep 2002 17:28:14 -0400


Good catch...it's fixed now (rev 1.10 of dbutil.c)

--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Friday, September 06, 2002 1:54 PM
To: TDS Development Group
Subject: [freetds] Re: dberrhandler() and dbmsghandler()


Il ven, 2002-09-06 alle 18:59, Steven J. Backus ha scritto:
> > In src/dblib/dblib.c we have definitions of dberrhandler() and
> > dbmsghandler()...
>
> This reminds me of another problem I have with freetds. Here's the
> msg_handler I use:
>
> int msg_handler(DBPROCESS *dbproc, DBINT msgno, int msgstate,
> int severity, char *msgtext, char *srvname, char
*procname,
> int line)

???

In our code
g_dblib_msg_handler(dbproc,
msg->msg_number,
msg->msg_state,
msg->msg_level,
msg->message,
msg->server,
msg->proc_name);

where is line parameter ???

freddy77



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






Archive powered by MHonArc 2.6.24.

Top of Page