![]() |
Attempting to update to 1.8.7 fails and breaks our database - Printable Version +- MyBB Community Forums (https://community.mybb.com) +-- Forum: 1.8 Support (https://community.mybb.com/forum-175.html) +--- Forum: Installation and Upgrades Support (https://community.mybb.com/forum-182.html) +--- Thread: Attempting to update to 1.8.7 fails and breaks our database (/thread-191386.html) |
Attempting to update to 1.8.7 fails and breaks our database - Monkeys - 2016-04-12
RE: Attempting to update to 1.8.7 fails and breaks our database - Destroy666 - 2016-04-12 Please start creating upgrade-related topic in the forum situated right below General Support - thank you. Moved there. (2016-04-12, 12:43 PM)Monkeys Wrote: Once that happened, I simply reverted back to the 1.8.6 files That's one of the worst thing you could do - don't do it. But good that you reverted the whole backup afterwards. What's your MySQL version, which system does your server run and what's the highest value you have in that postnum column (or just provide the value from the mentioned row)? RE: Attempting to update to 1.8.7 fails and breaks our database - Monkeys - 2016-04-12 Why is that the worst thing to do? If a backup fails and my forums are broken and inaccessible, rolling back the files & database to the backup I had is not a good thing? Current version: 1.8.6 SQL Engine is MySQLi 5.5.38 Running on a dedicated server with Windows Server Web Highest value for postnum is 3510. There are 8 entries that have -1 though, don't know why. I keep trying to run the SQL query "select * from mybb_users where ROWNUM = 599" but it returns nothing. RE: Attempting to update to 1.8.7 fails and breaks our database - Monkeys - 2016-04-15 Anyone? RE: Attempting to update to 1.8.7 fails and breaks our database - Monkeys - 2016-04-18 Am I allowed to bump threads? RE: Attempting to update to 1.8.7 fails and breaks our database - Monkeys - 2016-04-24 Well I don't know why this thread was ignored. Either way, big thanks to .m. for helping out. The issue was that some postnums were at -1 for whatever reason. Set them to 0 and that fixed it. |