Re: [Fofredux-devel] Something strange is afoot

[Kevin <ke...@dr...>]

> Ok - I've noticed this over the past couple of days - but only
> verified it this morning.
>
> When I'm reading feeds, I"ll choose "flag all up to this item". If I
> click on, say, the fourth feed, and then click "mark as read", I
> notice that what was supposed to be the next newest item is still down
> on the list (originally I thought it marked it as read), and items
> that were lower (or not there?) are now at the top, chronilogically.
>
> Perhaps this is something to do with the timestamp for ordering? I'm
> still investigating, but I wanted to put it out there for you devs to
> also keep an eye out for. Before you click "Mark as Read" on a number
> of flagged entries, see what the next item (that is unflagged) is and
> see if it's at the top of your items when you click "Read".
>

For identical values in the sort column (currently dcdate), it is not
guaranteed the item order will be consistent.

I see this often for feeds which don't include a pubDate or dcdate.  The
fallback is to use the cache timestamp.

We could change this behavior easily by using SQL and specifying 2 sort
columns.

"SELECT ... ORDER BY dcdate, id"

--=20
Kevin