Skip to Content.
Sympa Menu

freetds - Re: Odd problem round 2.

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "D. J. Hagberg" <dhagberg AT millibits.com>
  • To: freetds AT franklin.oit.unc.edu
  • Subject: Re: Odd problem round 2.
  • Date: Wed, 03 Jan 2001 04:38:34 +0000


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.

-=- D. J.




Archive powered by MHonArc 2.6.24.

Top of Page