NDB storage question
Hey! I am looking at storing a GPS path that is updated at a set interval, every X points I want to update the DB record. I'm trying to understand the best way to store this. Currently I have a table that shows the Activity: id | coordinates | date and had been updating the coordinates for testing and it worked fine.
In the docs there was a part about trying to limit array size to 5-10 but my approach would probably end up 500-1000 array size
https://docs.convex.dev/database/document-ids#trading-off-deeply-nested-documents-vs-relationships
Is this recommendation more so if i need to query the data vs storage safety? Otherwise are there any negatives to storing the gps points in a Coordinates table with a reference to the ActivityId for indexing / retrieval ?
In the docs there was a part about trying to limit array size to 5-10 but my approach would probably end up 500-1000 array size
https://docs.convex.dev/database/document-ids#trading-off-deeply-nested-documents-vs-relationships
Is this recommendation more so if i need to query the data vs storage safety? Otherwise are there any negatives to storing the gps points in a Coordinates table with a reference to the ActivityId for indexing / retrieval ?
Create complex, relational data models using IDs.
