mem usage large tables

[Shai-Hulud]

Hi all,

I's bulding my costum board and am planning to place it in mysql. Theres just one thing really I dont know. What would be best:

if I had say a topic and I wanted to show the number of replies at board index. Would it be best to simply count the ammount of posts in the topic table or would it be better to have a seperate colum wich contains the number of posts. the same counts for the last poster and the alst-post-date.

ofcourse when the table is small it would not be bad to count the whole table or look up the last poster but what if the table gets bigger, would this not seriously effect memory usage and loading speed?

your ideas on this,

thanks 🙂

[trex005]

If you have a database like postgreSQL that has triggars, it is great to have an external table that has all the counts, this by far is the most efficiant way to do it. on the other hand MySQL you have to be much more careful with your code to make sure you always handle the events properly where posts added, changed hidden deleted etc. if you are expecting very high volume then I would go for a secondary table regardless of the database!

[Shai-Hulud]

thanks for the reply 🙂

so mysql does not automatically make such tables so that when you call a function that counts the tables, it simply gives the values from the table?

this means I have to add a manual table thus?

thank 🙂