Re: AW: Problem with boolean column

> Perhaps we are talking about the known (and fixed) bug
> http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1131923

Yes, it seem this was the Bug i triggered.

> Appearance: 
> WHERE  <bool_col>    resp. WHERE    NOT <bool_col> 
> does not return the correct results 
>  
> Preconditions and circumstances: 
> <bool-col> added with ALTER TABLE .. ADD or being the last key column 
>  
> Workaround: 
> use WHERE <bool_col> = TRUE    resp.   = FALSE

The Workaround worked for me now, but why was/is "WHERE bool_col" not 
treated exactly the same way as "WHERE bool_col=TRUE"?

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx