(real) Archiv for vBulletin 3
 

I'm looking for an hack like that one from Xenon:
https://vborg.vbsupport.ru/showthrea...threadid=39104

why? I would like to have the achived threads/posts in another tables than the actual threads/posts for (search-) performance reasons.

there is no need for compressing the data - just move in another tables with no posting funktion inside.

any ideas?

THX,
sotty

*bump*

none? :(

why not modify one of the vbulletin files, i.e the admin .php that is used to move threads :) set up a new set of tables and mdify the .php to use them instead then you could maybe achieve it that way, soz for the crap reply but im no php expert.

that function will only "move" the threads from one forum to another; means, that the forumid in the db-row of that thread is changed.
but no moving of postings will take place... :(

i'll look into the vb2 code of Xenon the next few days, maybe i get an idea...

so you want to be them to a completely different table after such a period of time?

hmm I might try if no one else is. Basically you want it so you can move threads to a completely different set of tables that are more or less stripped down versions of the thread and post tables vbulletin uses. Then a script like archive.php that displays the threads and lets you read them as well?

EDIT: Also reading though the thread a bit more do you want it to do this after a certain amount of time or do you want it to happen manually.

yepp!

different thread/post tables for perfomance reason...

that would be great! :)

yes

correct.

the reason is the following: huge forums like mine get performance problems when searching the big post table.
my archive has about 2 million postings. i won't prune it, so look for a posibillity to "archive" it.

i prefer the manual way: select a bunch of threads like in the "move threads" option in CP and the chosse "archive", with the option "keep original threads" or prune it.

the archive don't have to be compressed like in Xenons hack, because that would cost to much performance when moving.

thx in advance! :)

if you have questions...

scotty

Feel free to do so, but for vb3 it's not that easy anymore, regarding that damn threaded mode ;)

As for the compression thing: the compression doesn't cost that much performance, the more intesne thing is to remove the old thread from the DB, because the searchindex has to be updated, and that's the real intense thing...

that means: if you have the mysql4 fulltext search enabled, the transfer would be much faster?

threaded mode isn't such a big problem for me... it's disabled in my forum, cause of the (normal) size of my threads... there are too big.

scotty