Skip to Content.
Sympa Menu

freetds - RE: [freetds] TODO reviewed

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Thompson, Bill D (London)" <bill_d_thompson AT ml.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] TODO reviewed
  • Date: Tue, 12 Apr 2005 13:35:40 +0100

Hi Guys,

I'll have a go at ct_options().
I had started to look at it anyway.

I reckon that the ctlibrary ct_options(CS_OPT_CHAINXACTS),
and its partner "SET" option "SET CHAINED..",
are the same as SQL server's "SET IMPLICIT_TRANSACTIONS ON"
command. They seem to be the same thing as far as I can tell.

Would someone like to verify that for me?

Bill







-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Lowden, James K
Sent: 11 April 2005 21:02
To: FreeTDS Development Group
Subject: RE: [freetds] TODO reviewed


> From: Michael Peppler
> Sent: Monday, April 11, 2005 1:08 PM
>
> On Mon, 2005-04-11 at 18:16, Lowden, James K wrote:
> >
> > 1. DBD::Sybase seems to send "COMMIT TRANSACTION" with no
corresponding
> > BEGIN TRAN. It uses ct_options to set CS_OPT_CHAINXACTS (0x07) but
> > ct_options is a one big noop:
>
> You can build it to not use CS_OPT_CHAINXACTS and to use explicit
> transactions (for AutoCommit OFF mode) instead.

Well, looking over the results of "make test" for DBD::Sybase, I can see
merely rebuilding it not to use CS_OPT_CHAINXACTS will still leave a lot
broken. I *think* making that ct_option work shouldn't be too hard, and
it would be a step in the right direction.

> You probably want to get the latest 1.05_01 for this - it fixes a
couple
> of problems with this specific issue.

I took your advice. Turns out I had 0.90 installed.

> > 2. The placeholder logic seems not to pass valid SQL to the server.
> > Look at this code from t/exec.t:
> >
> > my $sth = $dbh->prepare("exec sp_helpindex \@objname = ?");
> > ok(defined($sth), 'Prepare sp_helpindex');
> > my $rc;
> > $rc = $sth->execute("sysusers");
>
> There are two placeholder uses in DBD::Sybase. The one that is
exercised
> by t/exec.t is actually using the RPC functionality
> (ct_command(CS_RPC_CMD) and ct_param()).
> The one exercised by t/place.t is the "real" ct_dynamic()
functionality
> (i.e. "select ... from foo where bar = ?").

Thank you. The new pod mentions "exec" explicitly; the old one didn't.
It's much clearer now. It seems to me that the rpc functionality is the
less hairy for FreeTDS to fully implement (given that Sybase::DBlib
already works). But I know Bill wants to see DBD::Sybase placeholders
working; maybe I can help.

--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 we do
not accept
account orders and/or instructions by e-mail, and therefore will not be
responsible
for carrying out such orders and/or instructions. If you, as the
intended recipient
of this message, the purpose of which is to inform and update our
clients, prospects
and consultants of developments relating to our services and products,
would not
like to receive further e-mail correspondence from the sender, please
"reply" to the
sender indicating your wishes. In the U.S.: 1345 Avenue of the
Americas, New York,
NY 10105.
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------




Archive powered by MHonArc 2.6.24.

Top of Page