Feature proposal #7119open
Further improve SQL structure
The database structure of some tables can be improved further to increase performance. Changes suggested as follows.
Remove the id column and make user_id | asset a unique index. A user can only follow an asset once. id primary key doesn't make any sense here.
Same here. Remove primary key id and add unique index on user_id | type | item as you can't hide the same thing twice.
Again, same. Remove primary key id and add unique index on user_id | asset as you can't like the same asset twice.
I would like to do the same for tags, but since tags accepts tagging someone that isn't a user (e.g. tagging a name) it won't be possible to index that unique by user_id | asset | tag. Also if #6969 doesn't happen then give the read table same unique index treatment.
All the above changes need significant testing to ensure they'll actually bring performance gains.
No data to display