FreeTDS Development Group

[Tim Uckun <tim AT diligence.com>]

At 04:38 AM 1/3/2001 +0000, you wrote:
> Tim Uckun wrote:
>
> > OK I tried it with each field by itself and it segfaults on the "done]
> > [bit] NULL" field.
> > All other fields pull in fine.  I tried with a couple of other tables and
> > the same story.
> > If the select statement returns a bit field AND any of the bit fields
> > contains a 1 or 0 then it segfaults.
> > It returns a 104 error message for each row in the query which contains a
> > bit field that is not null.
>
> Ahh...  This might point to some unsupported datatype problem.
> Historically, Sybase's bit fields would not allow null -- they always
> had to be "not null".  Perhaps MS extended the protocol to allow a null
> bit field by defining a new datatype?  Not sure where one would fix this
> in FreeTDS, though.

It works fine on nulls though it only fails when it tries to print 
(convert) an actual value. The value does not matter BTW either 0 or 1 will 
cause the segfault.
----------------------------------------------
             Tim Uckun
      Mobile Intelligence Unit.
----------------------------------------------
   "There are some who call me TIM?"
----------------------------------------------