Rounds
Reputation: 1889
wordpress - Big post IDs, is it Okay in the future?
A client of mine has requested that a list of posts would be fetched through a data feed and a cron job will run each 6 hours to delete all the previously fetched data and add new data as posts.
The data is about 250 posts, fetched each 6 hours. My concern is about the posts IDs of this blog will get very very big in about 6 months from now.. for no reason!
Should I do something about it? Like for example trying to edit the posts instead of deleting and adding (while this might be a stupid workaround, it will slow down post IDs increment for no reason)
Thoughts please, Thanks!
Upvotes: 0
Views: 185
Answers (2)
user29410512
Reputation:
Do You Mean Permalinks? If so, if your worried, use Pretty Permalinks
Upvotes: 0
Related Questions
- Best practice to store a lot of IDs into the database to search it in the future
- postgres: id auto-increment with millions of rows per day. is it bad?
- Is it OK to have lots of IDs in a MySQL query using IN
- Is it safe to store Tweet IDs as BIGINTs?
- What type of id i need to chose if i want to work with huge id values in a future [ MySql ]
- Handling large data in php
- Is 170 mb of database is too large just for 350 posts?
- Will large strings, instead of auto-increment numbers, as ids affect my database performance?
- mysql bigint(250) overkill or not / max field size
- Is there a benefit to starting MySQL data base id at a large number?