Closed bbelderbos closed 2 years ago
Let's already account for multiple stores, so the store would be an enumeration (android, apple for now) on the app table.
Relations can be a bit tricky but they are explained well here: https://sqlmodel.tiangolo.com/tutorial/relationship-attributes/define-relationships-attributes/
The 1-to-many app <> metrics is because the app will have various metrics associated over time, so the metrics rows should have a date when the data was taken and a column per metric, makes sense? That would be my take, open to any suggestions though.
Great work, this is done
As discussed 1-to-many
-- to - many: Metrics (focus on first) -- to - many: Comments (focus on later)
Data as scraped here: https://github.com/gtossou/appscraper/issues/1
Can use SQLAlchemy but SQLModel is a nice abstraction that uses pydantic = type hints, better docs too: https://sqlmodel.tiangolo.com