Skip to Content.
Sympa Menu

freetds - RE: [freetds] ODBC RPC

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO Frediano" <Frediano.Ziglio AT vodafone.com>
  • To: "Rogers, Tom" <tom.rogers AT ccur.com>
  • Cc: freetds AT lists.ibiblio.org
  • Subject: RE: [freetds] ODBC RPC
  • Date: Thu, 7 Aug 2003 09:59:04 +0200

>
> Thanks for the help.
>
> Some status with last nights build regarding RAISERROR: I
> seem to get the
> errors/diag recs that SQL generates when I do something bad
> (say like SELECT
> from a table that does not exist) but not those that I
> explicitly call in my
> Stored Procs. You should see the same thing...just put the stmt:
> RAISERROR('HELLO WORLD', 11, 1)
> in an SP. You never seem to get it. However, but the
> statement: SELECT
> foo FROM bar
> in and SP and sure enough, you get that error.
>
> The errors get raised just fine in regular ODBC using MS SQL
> driver (I have
> some common code that uses UNIXODBC/FreeTDS on Linux, or
> builds on WinNT to
> use MS OBDC). I get different results...the Linux version
> using FreeTDS
> loses the RAISERROR, the WinNT ver gets it.
>
> I have included the dump.txt. I am calling the stored
> spTestProc, which
> calls RAISERROR returning the text: "An error was
> encountered." I see the
> error text in the dump, just not available through ODBC API
> when I call
> SQLError (it gives -2, invalid handle).
>

Oh... you are using SQLError, I'll try with it (usually I use
SQLGetDiagRec).

> <<dump.txt>>
> Also... how in the heck do I bind and send DATETIME variables
> to an SP.
> That doesn't seem to work via SQLBindParameter using SQL_C_DATE. Any
> advice?
>

No, can you post a small test ?

bye
freddy77




Archive powered by MHonArc 2.6.24.

Top of Page