Feature proposal #6969
closedImplement relationship table
100%
Description
This should handle who has access to the specified object. Specifically this will be used for notifications and conversations to determine who should receive the notification (probably remove the user parameter at this point) or conversation (conversations will use normal comment table). This reduces the replication. So for example instead of sending the notification to 5,000 users you'd create the notification once and it'd have 5,000 relationship entries which would be significantly faster to filter and contain less data. Example table structure as follows.
id | user_id | type | item
4 | 42 | notification | 32
Basically same as hidden table. Unsure yet if this should also apply to activity, but isn't likely necessary since activity needs to remain more dynamic. Depends a lot on the performance.