Skip to:

Re: Unread Topics

SamBauers: Hmm ?

The current implementation has one row per user per topic as it is. Instead of using something like time, I use the topic_last_post_id from the topics table. Then I have a table which essentially is user_id | topic_id | post_read. Which contains the very last post in a topic the user has read.

The implementation is far from perfect, the code that updates the table is getting run each time a post is rendered. Which means 29 useless sql updates per page.

I just need to get some time to look at the code to find another way. But as it is, it works.

I suppose I’ll be more involved, as there are some features I need to make for myself. I see no reason not to share the work.

Skip to toolbar