On Tue, Jan 20, 2009 at 4:00 PM, Miles J <[email protected]> wrote: > > What if there are like 1000+ unread threads, with thousands of users.
Again, if you're using MSAccess, this might be an issue. With, say, Postgres or MySQL? Not so much. > Why would I want to store all that information in the system. For the same reason you might want to be able to display which threads are unread. It's not something you have to do but, if you want it, you'll need to record the information somewhere. > 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. I don't understand what your concern is here. It's not as if you'll be selecting *every* thread, and *every* user's thread info at once. Say you want to get the comments that a user has seen already. When the user selects a thread/post/whatever to view, grab that user's coments_seen (or whatever) data, which should simply be a list of comment_ids. As for updating, again, this is something that's unnecessary *unless* you want to save a record of which threads a particular user has seen. If so, simply update the threads_users table when it's selected. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
