[freetds] ODBC unit tests "funccall" and "transaction"
Lowden, James K
LowdenJK at bernstein.com
Fri Jan 9 15:34:04 EST 2004
> From: Frediano Ziglio [mailto:freddyz77 at tin.it]
> Sent: January 9, 2004 3:21 PM
> Il ven, 2004-01-09 alle 17:46, Castellano, Nicholas ha scritto:
> > So, I've changed a whole bunch of variables at once: upgraded to
> > unixODBC-2.2.7, updated to latest FreeTDS sources with
> > Freddy's workaround,
> > compiled and installed FreeTDS, and now things have got
> > worse. Five ODBC
> > tests now fail against both Sybase and SQL servers, on my
> > 32-bit NetBSD system.
> :((( Yes and no... going deeply with problem I realized that
> I was using
> 2.2.6 version, not 2.2.7... Doing debugging (using compiled unixODBC
> with debug info) I realized that last updates do not handle state
> change very well (see line remove the SQLNumResults call in unixODBC
> ChangeLog on website). For this reason SQLMoreResults works but next
> SQLFetch ALWAYS fails (without even calling driver) so
> multiple records
> do not work as expected... also a metadata function fails if called
> after a SQLExecDirect... These test:
> - t0003
> - tables
> - moreandcount
> - earlybind
> are so expected to fail using unixODBC 2.2.7 due to unixODBC
> bugs. So we
> left with only funccall test (as before).
Testing independently with unixODBC-2.2.7:
$ grep FAIL nohup.out
Freddy, I don't understand. Is this a problem with unixODBC-2.2.7 that they
have to fix, or a problem with FreeTDS? Do we have to fix our code, or
write workarounds to their implementation, or just wait for their next
It's OK with me if we ship 0.62 with the caveat: "Works with unixODBC-2.2.6
and not with unixODBC-2.2.7. For unixODBC-2.2.7 support, wait for
unixODBC-2.2.8 (or, wait for FreeTDS 0.62.1 or 0.63)."
Most important is to be clear with the user about what he can expect. Tell
me what I should say.
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.
More information about the FreeTDS