I'm working on a Windows 8.1 app which needs to store and sync some data with a server. I'm not going to give the exact details because it would complicate this, but I will use an example.
I have a closet full of shoes. Each closet has a few shelves, and each shelf has multiple pairs of shoes. I have to store each closet in my db and remember how the shoes are placed(on which shelf and on which order). So I thought my db should have these tables: - closets - shelves - shoes Each pair of shoes will have a shelfId, and each shelf will have a closetId.
However, I estimated that in the shoes table I will insert ~1 million rows per year, so I'm worried that the db will grow too much. That's why I thought I could create only the table for closets, and each row will have a list of shelves serialized as JSON string.
I don't have to make queries in the data of the closet, I just need to store the content of the closet so later the user can view it again in the app. Do you think it's better to use JSON? Or should I create tables for shelves and shoes? Thank you!
Aucun commentaire:
Enregistrer un commentaire