Site Rollback Information, please read!

[Kill_the_Bug]

Any updates on the mapping discussion forum? I'm noticing a couple of missign posts.

[Fr0Z3n]

Quote:

Originally Posted by Kill_the_Bug

Any updates on the mapping discussion forum? I'm noticing a couple of missign posts.

Nothing yet, we haven't set up the backup database.

[Kill_the_Bug]

Ok cool - thanks for the update on the update!

[Tom Hoen]

You guys are doing great and hopefully you get everything working as intended!

(I wanted to cheer you guys!)

[henke37]

Quote:

Originally Posted by stevethepocket

Ah. So it sounds like my guess was partially right; the column that holds the "what forum does this thread go in" ID had all of its values set to the same number. I bet that could have been fixed with a little SQL-fu without resorting to rolling back the whole forum, honestly. It would just be a matter of copying the associations from the backup and then moving the leftover threads manually.

Yup, but they seem to be too lazy to do that.

[Fr0Z3n]

Quote:

Originally Posted by henke37

Yup, but they seem to be too lazy to do that.

I've had a couple people to come to me saying "no no no, this is actually really easy!" I honestly don't know the coding needed to do that, so that would be some drp would do.

The only issue that I would see with doing a sort function is merging the old w/ new. All post that are older than 3 weeks would already be there so would there be an issue with use ending up with copies (which we don't want), would it replace itself? Or would it be able to properly fit itself inbetween the old and new?

[stevethepocket]

What I would have done — assuming the database is structured the way I think it is — is write a run-once PHP script that performs a process like this:

retrieve thread #'s and subforum association #'s from the threads table in the old DB
store that mess in an array
for each row in the array:
- find the row in the current DB with the same thread #
- set the subforum association # in the current DB to the one in that row of the array

Then it'd just be a matter of finding the leftover threads, the ones that were made since the backup, and putting them where they belong manually. I assume that could be done through the VBulletin control panel.

Now that we've already started running off the backup, though, it's gotten a lot more complicated, because now we've got all the posts and threads that have been made since the rollback, which have the same #'s as the lost posts. Off the top of my head I'm not sure what we'd do about those.

[henke37]

update oldTopics, newTopics set newTopics.forumId=oldTopics.forumid where newTopics.topicId=oldTopics.topicId

Very complicated. Certainly not something I threw together in 10 minutes.

[stevethepocket]

Or that.

[Kill_the_Bug]

Quote:

Now that we've already started running off the backup, though, it's gotten a lot more complicated, because now we've got all the posts and threads that have been made since the rollback, which have the same #'s as the lost posts. Off the top of my head I'm not sure what we'd do about those.

Why don't you just lock the forums so no posts can be made until everything else is reloaded so that to don't have to wory about the duplicate / overwirte issues from happening? The once you have done that - you can then repost anything new so that it gets a new number in the proper order?