Skip to Content.
Sympa Menu

freetds - RE: [freetds] DBD::ODBC (0.45), MS SQL, unixODBC, FreeTDS (CVS) , bind_param_ino ut

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Frediano Ziglio <freddyz77 AT tin.it>
  • To: FreeTDS <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] DBD::ODBC (0.45), MS SQL, unixODBC, FreeTDS (CVS) , bind_param_ino ut
  • Date: 02 Jan 2003 19:18:46 +0100

Il gio, 2003-01-02 alle 18:36, Lowden, James K ha scritto:
> > From: Chris McDaniel [mailto:Chris.McDaniel AT telus.com]
> > Sent: January 2, 2003 10:09 AM
> >
> > It looks like result sets
> > are coming back OK now which is great
>
> Good! :)
>
> > looks like I'm missing output where
> > the stored proc uses the (T-SQL) 'print' statement.
>
> A "print" statement's output would be passed as an out-of-band
> server-originated message, not as data, similar to the "Changed language
> setting to us_english." message you may see when you log on. One small
> difference: "print" statement messages have a "message number" of zero.
>
> In db-lib, the client provides a "message handler" callback function that
> the library invokes whenever a server message arrives. I don't know how
> that's done in ODBC, or how well we support it.
>

In ODBC this is done using error reporting procedures. Using new API
(SQLGetDiag*) many warnings/errors can be returned. But this require
full rewrite of error handling (error now is global while should be
related to environment/connection/statement).

> tsql used to ignore them; I just committed a change to print them instead.
>

freddy77






Archive powered by MHonArc 2.6.24.

Top of Page