FreeTDS Development Group

["James K. Lowden" <jklowden AT speakeasy.org>]

D.J. is dead on!

from http://larr.unm.edu/~owen/SQLBOL70/html/ba-bz_7.htm:

bit (T-SQL)

Integer data type that can be 1, 0, or NULL.

Remarks

Columns of type bit cannot have indexes on them.
Microsoft® SQL Server optimizes the storage used for bit columns. If there 
are 8 or
fewer bit columns in a table, the columns are stored as 1 byte. If there are 
from 9
to 16 bit columns, they are stored as 2 bytes, and so on.

"Well, bit fields tend to only contain 1 or 0."

True enough for *Newtonian* bits, sure.

--jkl


"D. J. Hagberg" 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.
>
>                         -=- D. J.
>
> ---
> You are currently subscribed to freetds as: [jklowden AT speakeasy.org]
> To unsubscribe, forward this message to $subst('Email.Unsub')