Normally I would not ask ……..
Why do you want to do this ?
Is there a problem with something ?
Thread Starter
jackfr
(@jackfr)
You’re right 🙂
But I am asking for that because I will bulk import a great number of listings, do not want those listings would begin with a too big custom post ID (=listing ID).
Hoping I explained this correctly.
Regards,
Jack
> do not want those listings would begin with a too big custom post ID (=listing ID).
Again.
**Why**?
Realistically, the short and general answer is that it would be a very bad idea for you to be changing post IDs. There are database relationships using the Post ID between the Post and things like Revisions, Comments, Drafts, Thumbnails, meta-data, etc, etc, etc.
If there is a problem you are trying to solve, pls describe.
Otherwise, having a ‘high post ID number’ is not an issue that needs resolving.
Thread Starter
jackfr
(@jackfr)
In the past, I have used the website to test a lot of listings, but I have already removed all of those unused listings, in order to bulk import new listings to the real website (that I will put online).
That’s why the current ID is now very high.
And that’s why I think of returning to a much smaller listing ID for the new listings.
(There is no issue indeed, just do not want to begin the new listings with such a too high ID).
Even that, is it still a bad idea, according to you?
> There is no issue indeed
Correct!
🙂
> Even that, is it still a bad idea, according to you?
Definitely.
The post ID field (and the IDs for most things) are 64 bit unsigned integers (BIGINT), allowing 18,446,744,073,709,551,615 values. You’ve got room to grow.
Thread Starter
jackfr
(@jackfr)
(@corrinarusso), (@sterndata)
Thank you, I follow your advice then 🙂