FreeTDS Development Group

[Dossy <dossy AT panoptic.com>]

On 2001.07.26, Ian Harding <ianh AT tpchd.org> wrote:
> Well, I looked in my server.log and guess what I see?  Tons of 
> 
> Notice: Ns_FreeTDS_Msg_Handler(envision): <error message> 
> 
> messages.  Doh!  I thought I looked there.  In fact I did, but I was
> looking for 'Error:'.

What's interesting is that it's the Ns_FreeTDS_Msg_Handler that's
logging, not the Ns_FreeTDS_Err_Handler.  That's why it's being
logged at "Notice:" level and not "Error:" level.

> I did not wrap the ns_db call in a catch [] because I figured if there
> was an error I would just get an ugly 'Could not process this request
> due to an error at the server' message and I am just testing at this
> point.  These errors seem not to cause that to happen.

Yeah, AOLserver unlike Apache doesn't just chuck a useless "Server
Error" message just because one simple stupid error on a page.  It
just takes the chunk of ADP that threw the error and discards it,
serving up the rest of the page regardless, and dumping an error
in your server.log.

IF you want to trap errors in your application, you'll have to
[catch] them ...

> They are definitely not in my tdsdump logs.

And as Brian showed us from token.c, since nsfreetds registers its
own private error and message handlers, they won't be dumped into
the tdsdump logs.  Perhaps mildly confusing, but it does work as
expected ...

> I am my own worst enemy sometimes.  Oh well, at least I got you on the
> list!  Thanks for your time!

Heh, heh!  I guess since I am developing against libtds, it's
only fitting that I sit on this mailing list, huh?  ;-)

I'm just happy that nsfreetds works, against both MS SQL Server
and Sybase ... ;-)

-- Dossy

-- 
Dossy Shiobara                       mail: dossy AT panoptic.com 
Panoptic Computer Network             web: http://www.panoptic.com/