I have a requirement where the client has some news (and other items) which are only available to logged in members. They want to show each member if the item is "un-read". I am thinking about using relations for this i.e. when a member reads the item it will create a relation between the member and the content. I can then check if the logged in member has a relation with the content and show it as "read".
Is this overkill? There will be a fair amount of content (1000's) and a few hundred members, so potentially a lot of relations!?
Another way is to create some custom tables to store which content members have read.
Has anyone implemented anything like this and can offer advice on the best approach?
Personally I would go down the seperate table for this, just store the nodeId and the memberId in the table on page load. There'll be a slight overhead for every news item on page load due to having to perform a lookup on the table to verify "if read".
Member "Unread" Content
Hi,
I have a requirement where the client has some news (and other items) which are only available to logged in members. They want to show each member if the item is "un-read". I am thinking about using relations for this i.e. when a member reads the item it will create a relation between the member and the content. I can then check if the logged in member has a relation with the content and show it as "read".
Is this overkill? There will be a fair amount of content (1000's) and a few hundred members, so potentially a lot of relations!?
Another way is to create some custom tables to store which content members have read.
Has anyone implemented anything like this and can offer advice on the best approach?
Version 7.1
Cheers
Chris
Personally I would go down the seperate table for this, just store the nodeId and the memberId in the table on page load. There'll be a slight overhead for every news item on page load due to having to perform a lookup on the table to verify "if read".
is working on a reply...