From: Andrew T. (nilspace) <nil...@us...> - 2006-04-07 18:59:32
|
Well, by default, the column values are NULL, so when the "view unread" gets all the NULL, then that's ok. However, the fof_update_item_flag takes FOF_UNREAD_FLAG, which was NULL (I changed it in init.php to 0). With NULL, and the SQL query via ADODB sets the flag to 0 (at least in my testing), which then doesn't have it show up when the get_items() looks for all items with flag =3D NULL. So, ADODB on MySQL appears to set NULL as 0. Andrew On 4/7/06, Kevin <ke...@dr...> wrote: > > > The potential solution has been committed to CVS. It will be released > > in 0.3 (which is 'imminent' and also 'emminent' ;) Please keep up the > > great effort testing the Release Candidate. > > > > Dev notes: > > For some reason, even though the item was flagged to "unread" it > > wasn't then being picked up as unread. I think this was due to ADODB > > using "0" instead of "NULL" when it set the flag in the MySQL db. > > Therefore, items flagged as 'unread' will use 0 (thought still via the > > FOF_UNREAD_FLAG) to address this issue. > > What is the behavior of items in the database with the flag still set to > the old value indicating unread (NULL)? > > > -- > Kevin > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |