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: "James K. Lowden" <jklowden AT schemamania.org>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] ODBC - binary, row count and compatibility
  • Date: Tue, 9 Mar 2004 10:45:01 -0500

On Tue, 9 Mar 2004, "ZIGLIO, Frediano, VF-IT"
<Frediano.Ziglio AT vodafone.com> wrote:
> > Does Microsoft's version stop at the first DONEINPROC?
> >
>
> Yes. Assume that server return large text/image data on select, client
> cannot cache all rows so it has to stop at first recordset (I tested and
> it stops even if recordset is empty).
>
> > I don't understand how SQLExecDirect() can (correctly) stop before
> > DONEPROC. How is the application expected to learn of the ERROR?
> >
>
> I think on next SQLMoreResults or perhaps on SQLFetch (I didn't test
> it)...
> From lang_error test calling SQLExecDirect("SELECT
> DATEADD(dd,-100000,getdate())") return SQL_ERROR.

OK. I'll look into this further.

This all started because I wasn't able to commit transactions in
DBD::ODBC. Only along the way did I discover that errors seemed be
masked. As long as DBD::ODBC uses ODBC correctly, and reflects errors
that occur inside stored procedures, I'm satisfied.

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page