[arcnmx]

Originally Posted by Reincarnate

I find that interesting -- so you're saying it's actually better to have it all in one table with well-chosen indexes?

How do you then decide what to put into another table and what to lump together?

Right. You could kinda say that indexes split up tables into many small minitables that are easy and quick to query.

Basically, if you're making multiple tables with the exact same column structure / holding the same data, you're likely doing something very wrong.

Originally Posted by Reincarnate

Although I guess it makes sense: If you have a table called "level_score_data" or something, it would just contain a key identifier (song ID or something) with the userid (person who played it) and the corresponding score. Then you could just query that to calculate the levelranks, yes?

Mmhm. The alternative, level_score_data9999 without a songid field results in mayhem and slowness.