> Each ticket was a column. So if your most active user had 5 tickets in total history, you needed 5 columns.
I was thinking like, "Oh yeah, they have 5 tickets, so need 5 rows. What's wrong?". And I read it again and found it's the word "column". It must be a big fun to write a query for such tables.
It would be _slightly_ better if the DBMS have array types.
Often they are not scalable, but it is better than thousands lines of copy-and-pasted code.
I was thinking like, "Oh yeah, they have 5 tickets, so need 5 rows. What's wrong?". And I read it again and found it's the word "column". It must be a big fun to write a query for such tables.