You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's list messages, in each one the user data from another users collection is repeated. This abundancy is causing extreme increase of data transfer. The optimal solution on joining two tables would be:
🔖 Feature description
Let's list messages, in each one the user data from another users collection is repeated. This abundancy is causing extreme increase of data transfer. The optimal solution on joining two tables would be:
In this example we call collection
messages
. Data from the collectionusers
are added through relationships separately without repeating.🎤 Pitch
The design of current implementation of relations is the worst possible.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: