Skip to Content.
Sympa Menu

freetds - Re: More on Crash in Python driver

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: More on Crash in Python driver
  • Date: Wed, 25 Sep 2002 15:38:27 -0400


I just checked in a fix for ct_cancel(). Let me know if that helps.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Wednesday, September 25, 2002 2:25 PM
To: TDS Development Group
Subject: [freetds] Re: More on Crash in Python driver


Nick,

Thanks for the help. Yes, I discovered that I was not thinking straight. In
switching between the ODBC driver and the direct-to-ct driver, I was still
using the ODBC DSN name instead of changing to the machine name.

I can now connect, and in fact, with a little tweaking, I have the driver
working.

The one problem which I had to fix was what I originally posted as the
crash: if the driver gets an error during the connection, it calls:
ct_cancel(CS_CANCEL_ALL);
which causes a segfault.

Is ct_cancel() fully implemented? Or maybe the problem is that the driver
should not call ct_cancel() when it could not connect in the first place?

Thanks for the help.

Paul

On Wed, 2002-09-25 at 11:03, Castellano, Nicholas wrote:
> OK...in that case, it seems that you're right, and the problem is that
> it's not finding the target host. Are you sure your freetds.conf is
> being found in the correct location? And you specified the SQL server
> name correctly?
>
> Cheers,
> --nick
>
> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> Sent: Wednesday, September 25, 2002 10:02 AM
> To: TDS Development Group
> Subject: [freetds] Re: More on Crash in Python driver
>
>
> I checked the code. The Python driver has a "HAVE_FREETDS" macro,
> which, in this case, is used to comment out calls to ct_diag().
>
> Paul Rensing
>
> On Tue, 2002-09-24 at 16:41, Castellano, Nicholas wrote:
> > Errrm...how is python calling ct_diag(), when it seems that FreeTDS
> > doesn't provide a ct_diag() implementation (not even a stub)?
> >
> > bash-2.05$ grep ct_diag include/* src/ctlib/*
> > bash-2.05$
>
>
>
> ---
> 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: [paul.rensing AT att.net] 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.






Archive powered by MHonArc 2.6.24.

Top of Page