just columns
What if there are a lot of things that can be customized. How do you store it for 1 million users?
you have a column per setting?
So if the app have 100 customizable thing, you will create 100 column in the table?
And later when the app have 200 customization, you add another 100 column? And for 1 million users, you create it for 1 mil rows?
yes you would create 1 million rows
You'd have to create them in the multiple dbs per user scheme as well
Ok. If I'm designing the app, I would just give each user their own DB for their own setting. Because if I had 1 mil user, removing 1 mil connection to DB just to get timezone should be much better
Your app won't support 1 million users with that design
right and opening 1 million files is so much better :D
You completely ignore that fact that finding the correct DB you need to open by a userid is not different than finding the relevant row in a single DB, and it'll have worse performance
ever heard about sqlite?
This discussion is about giving each user their own sqlite
Обсуждают сегодня