news [mailto:[EMAIL PROTECTED] Im Auftrag von Sven K�hler wrote: > > Hi, > > i have a serious problem with MaxDB 7.5.0.19. > There is a simple table with 3 columns, one of them is boolean. In > former times, the table looked like this: > > id test > 1 false > 2 true > 3 true > 4 true > > the value for the id 2 was set to false, but when i now execute the query: > SELECT * FROM table WHERE test > than i still get those results: > > id test > 2 false > 3 true > > Well, the database does return a "false" value, altough the WHERE-clause > forces a true there. Well - i have tried to recreate indexes (the column > test is indexed), to disbale the indexes, i checked the database > structure but nothing helps. > > Any hints what i could try next, or how to debug this problem? > >
Perhaps we are talking about the known (and fixed) bug http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1131923 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 As 7.5.00.23 is not released yet, please add = TRUE to the qualification. If this does not help, please let us know. Elke SAP Labs Berlin > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
