Skip to Content.
Sympa Menu

freetds - RE: [freetds] ODBC unit tests "funccall" and "transaction"

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] ODBC unit tests "funccall" and "transaction"
  • Date: Fri, 9 Jan 2004 15:33:06 -0500


> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: Friday, January 09, 2004 3:21 PM
>
> :((( 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).

OK, I can grab 2.2.6 and try that instead. If we can get everything
working, I would consider it reasonable to document that this release is
compatible with unixODBC-2.2.6 and not unixODBC-2.2.7.

If that will help narrow things down, I'm certainly willing to give it a
try. I can't remember whether you were able to duplicate the funccall
failure on your end or not...

> I'm sorry to have wasted your time...

No apology needed and my time hasn't been wasted. I think we're zeroing in
on the answer, I'm just short on time to work on it today to meet Jim's goal
of getting the release cut this weekend.

Cheers,
--nick
-----------------------------------------
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.






Archive powered by MHonArc 2.6.24.

Top of Page