Skip to Content.
Sympa Menu

freetds - RE: [freetds] ODBC - binary, row count and compatibility

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] ODBC - binary, row count and compatibility
  • Date: Mon, 8 Mar 2004 13:42:38 -0500

> From: ZIGLIO, Frediano, VF-IT [mailto:Frediano.Ziglio AT vodafone.com]
> Sent: March 8, 2004 8:05 AM
>
> Finally I found some time to fix some ODBC issues:
> 1- prepared statements and multiple recordset

This is very good. The row count issue was quite a problem.

I adapted most of these changes to the 0.62 branch, but I haven't committed
them yet. I'm not sure I want to, because it's getting to be a rather big
patch, and we still don't have a fix for the dropped errors. I'm beginning
to think we'll issue 0.63 rather soon, instead, depending on how much more
needs to be done. What do you think?

I changed the odbc/unittest/transaction.c procedure:

CREATE PROCEDURE testinsert @value INT AS
INSERT INTO TestTransaction VALUES ( @value )
SELECT * FROM TestTransaction
select @value / (@value - @value)

(if you pass the procedure an argument). Here's the output:

EXEC testinsert 1
EXEC testinsert 2
DROP PROCEDURE testinsert
DROP PROCEDURE testinsert
CREATE PROCEDURE testinsert @value INT AS
INSERT INTO TestTransaction VALUES ( @value )

EXEC testinsert 1
EXEC testinsert 2
DROP PROCEDURE testinsert
DROP TABLE TestTransaction
Done.

:-(

I'm still not sure how to go about fixing this.

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






Archive powered by MHonArc 2.6.24.

Top of Page