No, not through the database. I am doing it through the ACP....and it does NOT automatically sync them...as evident in both pictures. It may show proper in the member list, but in the database the number jumps from the last user (my moderator, number 54) to 166.Oyabun1 wrote:If you delete users using the built in functions using the ACP member numbers are automatically synchronised.
Did you delete users directly from the database?
Awesome, Thank You very much...that did it.Brf wrote:RUn this SQL in phpmyAdmin:Where 60 is the next number you want.
Code: Select all
ALTER TABLE phpbb_users AUTO_INCREMENT = 60;
I do realize that a major benefit would not be readily shown, and most likely is not a long term issue that would cause problems, but for nit-pickers like me, the accuracy in the member count would be the benefit...take this site for example...the memberlist page shows total members is 429,970, but the newest member (at this time/posting), whos username is 22football, is showing as user number 1,347,482..BIG discrepancy...so even though the usercount is showing proper, the database user count is wayyyy off. Not sure how many other people would be concerned with it.Oyabun1 wrote:In order to gain support you will need to clearly show what benefit this change would bring, so good luck with that.
That I do understand! I may submit it...but I might first dig through the code to see if I can make the MOD myself, then submit it as such...that way others can pick and choose...I just needed the "bump" as to where to begin...which I received..Mick wrote:The problem is, if every conceivable option/hack/MOD or whatever was introduced (for nit-pickers ) to the core code, before long you would need a terabyte of webspace before you got started. I'm not arguing one way or the other whether or not this would be beneficial to a lot of users but the path Oyabun1 mentioned, [3.x] RFCs, is the way to go. If it's accepted it will be added.
Suppose not the latest member is deleted but a member that has newer members after him/her.Tux_Rules wrote:Any way to add this to the base code so that when a spammer is deleted or any other user is deleted that it reads the last user id number and automatically corrects for the next new user?
Figured that one out about an hour after posting my last comment and had time to really contemplate what all it would take. It is beyond what I would want to try and tackle for my level of experience, though I am sure it could be done.HGN wrote:Suppose not the latest member is deleted but a member that has newer members after him/her.Tux_Rules wrote:Any way to add this to the base code so that when a spammer is deleted or any other user is deleted that it reads the last user id number and automatically corrects for the next new user?
That will make a hole in the database numbering (userid) as well. It will not do to only read the last used number, but requires renumbering of all users after that deleted member.
However synchronising the user table will give problems with many other tables, synce they are related through the user_id. So it requires updating userid in many other tables, e.g. posts, topics, groups, permissions, etc.
I agree that it won't be worth the time to do (made my brain hurt just thinking of what it would entail to make the code to update and keep things in order ). I had asked for the help for my own nit-pickyness and I do realize that it should have no adverse affects on how the board runs.Lumpy Burgertushie wrote:well anything can be done. however something like this is probably not going to be worth anyone's time.
I have never seen a request for something like this before. people just dont usually care about the ID numbers staying in order. It has no effect on how the board runs etc.