Tara ,'Get It Done'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
is that the main problem?
It isn't yet, but it will be. I'd hate to have to react to that in a panic, the same way as we're having to react to the server load issue.
As for load, keeping them in the database in a different table offsets them from being part of the day-to-day processing, but I have a suspicion that since the database will still have the same number of records, with the overhead of having more tables that it will still drag it down. Much less, but it will still be a factor.
I don't get this ita. What's taking up 262MB of space if not the database?
I will check with support.
since the database will still have the same number of records, with the overhead of having more tables that it will still drag it down.
So the archives couldn't live in a completely separate database from the active threads?
Oh, wait, I get it - It would still have to be connected to the user table, and maybe others. Is that it?
It would still have to be connected to the user table, and maybe others. Is that it?
Yupped. The sucking options take care of that, since info is embedded. But the separate database would still be quasi-live, and reflecting stuff like a user changing their tagline, etc.
Can we set the search default to be subscribed threads? Or is that less usable, you think?
Yupped. The sucking options take care of that, since info is embedded. But the separate database would still be quasi-live, and reflecting stuff like a user changing their tagline, etc.
Right. It would be like the Attic at WX. Rats, I'd hate to lose that functionality. Searching for something thread by thread is a huge pain.
Can we set the search default to be subscribed threads? Or is that less usable, you think?
I'm still subscribed to every Natter thread. Just never bothered to unsubscribe because the fall to the bottom of the list anyway. I can't be the only one who does that.
The sucking options take care of that, since info is embedded.
Damn straight! :)
I'd hate to lose that functionality.
It would be annoying, but it seems like a small price to pay.
I still support the idea of sticking the archived threads off the main site.
What about an ashes board? Same basic structure and user table, but all the threads closed (of course).
I'm still on coffee cup one. This might not make much sense.
But, so long as we hosted it elsewhere, you could still search it like DX wants to be able to do, and it wouldn't drag the main site down.
I still support the idea of sticking the archived threads off the main site.
As html or as a database?
What about an ashes board? Same basic structure and user table, but all the threads closed (of course).
How would the user table stay updated? Every time a new closed thread was ported, an update to the archives user table would be required.