Thanks for the link! Ugh, I was sure I've been at that manual not a
long time ago...
So a change from INT to TINYINT would save 4-1=3 bytes. We have to do
that for 3 columns so that make 9 bytes less for each row. If there
are 120k rows that makes about 1MB less. Doesn't seem so impressive
when there is 100MB database but is a good start
Some optimization is always better than no optimization.
I didn't understood what exactly INT(2) means? A number with 2 signs,
taking 2 bytes or it can display a number with 2 signs maximum taking
all 4 bytes as regular INT?