Skip to Content.
Sympa Menu

freetds - RE: [freetds] _SQLExecute clearing of current_statement member

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
  • To: "Aaron" <crackajaxx AT gmail.com>, "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Cc:
  • Subject: RE: [freetds] _SQLExecute clearing of current_statement member
  • Date: Tue, 3 May 2005 14:38:01 +0200

>
> FreeTDS version: 0.62.3
> UnixODBC version: 2.2.8
> Platform: Gentoo Linux 2.6
>
> I'm using DTL (and this could clearly be an issue with DTL) and I
> noticed an issue when performing a query on something that returns an
> empty set. The path follows its way down to _SQLExecute() and the
> statement succeeds. It performs a test and finds the value to be
> TDS_NO_MORE_RESULTS. It sets stmt->dbc->current_statement to null and
> returns SQL_SUCCESS. No problems so far.
>
> DTL in response to this calls SQLFetch which makes its way to
> _SQLFetch(). The call returns SQL_SUCCESS_WITH_INFO. The call to
> _SQLFetch() checks that the calling statement is the same as
> current_statement (which is now NULL) and it raises an error 24000
> indicating that the cursor is invalid.
>
> Any thoughts on this?

Try 0.63.
What does DTL mean?
I think DTL is till ODBC 2. Perhaps it expect data if SQLExecute
succeed. Are you using a DM or not?

freddy77



  • RE: [freetds] _SQLExecute clearing of current_statement member, ZIGLIO, Frediano, VF-IT, 05/03/2005

Archive powered by MHonArc 2.6.24.

Top of Page