Moving multiple posts (but not all) from one thread to another

bitch

Hey everybody,

The title almost says everything: I've got a thread where people started to discuss a second topic and the original topic now begins being lost. I would like to move all the new postings to a new topic.

I've seen that this is very easily managable in vBulletin (for example), because there you can check every posting which you'd like to move to another thread.

Is there a way to do this in Vanilla (without changing the database directly)?

Kind regards.

UnderDog

At this moment, there is no other way to move those posts but a MySQL query.
We have the wish at this moment to add the functionality to vanilla, but it's not in there right now.
Maybe something for a plugin?

bitch

Thank you for the quick reply.

I would love such a plugin, but I'm not that familiar with MySQL and how Vanilla integrates it.

So, theoretically: I start a new discussion, explaining that the following posts were moved to here from another discussion. After that I look up the old DiscussionID (for example 500) and the just generated DiscussionID (for example 600).

Then I'd execute the following query:
UPDATE `GDN_Comment` SET `DiscussionID`=600 WHERE `DiscussionID`=500 ORDER BY `DateInserted` ASC LIMIT 8,9999

8 indicates, that the first 8 posts are on topic, the rest should be moved. I didn't try this, because at the moment I'm not able to execute it on a test system.

1.) Would this work
and
2.) Would it be the most proper and tidy solution?

UnderDog

1.) yes, it would work
2.) I don't know if it would be the most proper solution, but it's exactly the same solution I would come up with :-)

bitch

OK, thank you very much, it worked. (:

For some reasony PhpMyAdmin told me there was a syntax error, as long I had LIMIT 8,9999 in there, but as soon as I removed it, it worked. I then moved them back to the right thread "by hand".

Thanks again!

Nevertheless, it would be awesome if upcoming Vanilla versions would have an inbuilt tool to do this! (:

tester13

Interesting thing that such functionality reveals Vanilla database and sorting rules flaws.
As you normally want to add posts after all existing posts, but in chronological order.
Otherwise you'll have unreadable mess from different threads.
This is why we need ThreadOrderID field in this table. And all sorts must also use it, instead of Data.