Implement Handling of The Feed (Database Table and Related Pages) #3
Labels
No labels
component: admin dashboard
component: api
component: backend
component: badges
component: blogs
component: content management
component: external notifications
component: faqs
component: friends
component: game reviews
component: game search engine
component: games
component: genres
component: internal notifications
component: lists
component: payments
component: platforms
component: profiles
component: security
component: site notifications
component: web design
dependencies
php
priority: high
priority: low
priority: medium
status: awaiting feedback
status: done
status: in progress
status: in queue
status: in review
status: needs investigation
status: wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: MyVideoGameList/myvideogamelist.com#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There's no point in having 1 million rows in this table. We should clean it nightly and trim it down to 100,000 rows. That should be more then enough data. I can't think of any reason why we'd want to keep really old stuff.As noted here I don't think I want to remove data, but we definitely need to figure out how to store older records. Perhaps one table can have up to 5,000 records whereas older data can be offloaded into another table or something.
Originally posted by josh87
Maybe you can trim it down by date?
@josh87 Yeah, I was thinking about how to do it. I was thinking just select 100,000 rows, truncate, then reinsert them. I have to remember which resets the auto-increment back to 1.
Originally posted by josh87
Well
truncate
will drop all records from a table and resetauto_increment
.I am not sure the value it would add to remove this data from the database on a periodic schedule. The only time I have noticed it going slow is when loading the Edit User page from the administrative dashboard side of things. I'd like to think this is a low priority issue at the moment.
We need to do some research and see if this page/functionality is really even used by anyone.
So people definitely do look at this page (I asked in our Discord server), so we'll need to figure out how to handle the feed. Ideally I don't want to remove any records but at the same time, the table is massive.