So I'm working on a (yes, yet another) stat plugin. I've got everything working and everything is fine. But I feel that the logic of saving the stats could be better. What I've got right now is a bunch of enums (think like COALORE_BROKEN, IRONORE_BROKEN, etc) and an object that keeps track of these breaks. In my SQL table, I've got every single player with every single stat on a different row. So I've got a row for Joe's COALORE_BROKEN, and another one for his IRONORE_BROKEN, and yet more for other things. I feel that it would be more both more friendly to future updates and more friendly to admins (if something needed to be adjusted) if I simply made a string that contains all of these things, and that is completely possible. The problem is that the string would be so long once players started breaking different types of blocks. Here's an example of what an entry could look like. Column: Value ----- username: Joe blocks_broken: 1:0;1|2:0;2|17:3;1 So basically, it would be a simple pipe-delimited string, with the format ID : DATA ; AMOUNT for each block. That's cool and all, but I'm just not sure that's the best way to do this. I mean, that would have only one row for each user, but I don't know if having a 10,000 character VARCHAR is reasonable. Thoughts?