- Jan 18, 2009
- Reaction score
What is (or will be) the status of all old threads? I haven't heard any official word yet if they're lost for good or if that's still being resolved.
Chris,Bump. I'm curious to know if any of the older threads will be brought back. I have a couple of build threads that I put a lot of time into that I'd like to see resurrected.
Thanks in advance.
That's option #2; the ideal (option #1) is to get them integrated in.
It's a really neat theory, but without knowing the database structure, I cannot tell you how easy it may or may not be.I don't see the problem with merging at all. The fact that all of the threads have a date and time attached makes the merge that much easier. In fact, due to the time lapse in between when the old forum went down and when it came back up again, makes it that much easier. The old threads would just be appended onto the new database file rather than 'merged' in between.
The old threads wouldn't necessarily have to be attached to their owners so long as the threads were still searchable. And the searching task is a function of the system software anyway rather than something that is inherent in the database model.
The only slight to the whole procedure would be the time it takes to accomplish the task- the delay in between when the new database is downloaded and uploaded again (with the appended data) would result in some lost threads. However, that's a small price to pay for the benefit of getting all that history back.
Of course, all this is moot if the data is not recoverable to begin with.It's a really neat theory, but without knowing the database structure, I cannot tell you how easy it may or may not be.
One potential nightmare is how to handle user IDs. Every post should identify who posted it, and ideally, if the data is merged, it should reflect that user's current ID. Which means the need to run a merge on the user data and figure out old versus new IDs -- folks may have changed IDs, someone else may be using the same username as someone else, etc. Lots of permutations, just on figuring out who to attribute each post to.
Once you do that, you then have to figure out how to get it all into the forum tables. Depending on how the code is written, it may confuse vBulletin if a message with a higher internal ID has an older date than a message with a lower ID.
Also, what about marking messages as read? vBulletin obviously tracks this at a fairly detailed level; while in the process of merging the data, every user is suddenly going to see years and years of messages appear as unread in each forum. But, if they go look, the first page shown would be the latest (by date) and they wouldn't see them, so they might think the software is broken.
I could go on, but I think you get the idea.
Theoretically, it's easy. Getting the computer to understand what you're doing and handle it appropriately isn't necessarily so easy.
The ID thing could be tricky. Although I kept my "handle" I have a different member number (now 74, before ??). If the old IDs use the member number, perhaps they could be massaged by adding 10000 or something to offset those members?If it was possible to merge the databases together, it does seem it might be too hairy to try to also merge new IDs with old IDs. But you know, whose fault it is that people changed their IDs? Not TRFs. I did not change mine, a number of others did not change theirs. Anyone who changed their old ID to a new one, if this was the only roadblock to merging the data back? Sorry....
If it was not possible to merge the data, then OK, as an archive. I presume an archive would be just that - No new posts, as new posts would be confusing and messy, even more so by those who had new IDs who were continuing old threads that their old ID had posted in.
- George Gassaway
That's a good option, but I think we should choose a name without "mold" in it.To avoid problems merging, a simple solution.
Just import the database into another site, such as rocketryforumold.com? All threads would be locked.
It would preserve the information, be searchable, and not damage this one.