Hey, that's great you considered my notes. I'm honored =) .
Actually if you try to keep your code dry you could also expand this principle to cover your database design, too. Why not only have one stats table instead of three or more? Simply call one column "type" again (with ENUM) to choose which stats you want to select, add, delete or update. I haven't read the whole code absolutely attentively, but I ran over it ;) . The tables seem to be pretty exactly the same.
Greetings from FEtMab Sepp
Luke
· 1 year ago
Thanks for the tip, sepp - I'll have to look into that as well(it looks like this will be the week of re-designing for DRY =P)
All Comments
Actually if you try to keep your code dry you could also expand this principle to cover your database design, too. Why not only have one stats table instead of three or more? Simply call one column "type" again (with ENUM) to choose which stats you want to select, add, delete or update. I haven't read the whole code absolutely attentively, but I ran over it ;) . The tables seem to be pretty exactly the same.
Greetings from FEtMab
Sepp