As I mentioned earlier, this wouldn't be accurate. A user can log in but not read certain threads. Think of an email client--when I open Thunderbird, I expect that any unread messages will remain in an "unread" state regardless of when they were sent.
On Wed, Jan 21, 2009 at 8:39 AM, mark_story <[email protected]> wrote: > > Couldn't you just compare dates? Compare the last time the person > logged in with that of all the most recent posts. Then in the session > all you need to do is track which ones have been read, and unhighlight > those in the view. I don't think there is really a need to store this > in the database. > > -Mark > > On Jan 20, 4:00 pm, Miles J <[email protected]> wrote: >> What if there are like 1000+ unread threads, with thousands of users. >> Why would I want to store all that information in the system. Plus I >> would also have to extract the array from the database, remove indexes >> depending on what threads they have read, update the db again, etc. >> >> Anyways, anyone have answers to my initial questions? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
