aarku
aarku
CCConvex Community
Created by aarku on 4/18/2025 in #support-community
Plans to support functions returning delta updates?
I have a question about the use case where you are subscribing to a query that returns a large array of data that changes often. Are there any plans to officially support smartly returning only the changes, rather than the whole array every time? Similar to how Firestore and Realm ( called MongoDB Atlas Device SDKs now) behaves. Thanks!
16 replies
CCConvex Community
Created by aarku on 4/15/2025 in #support-community
Recommendation for securely serving files > 20 MB
I've read the docs about serving files from HTTP actions, which allows you to implement access control. What does Convex recommend I do for files larger than 20 MB, if I want access control? Thank you, -Jon
2 replies
CCConvex Community
Created by aarku on 11/15/2024 in #support-community
Guidance on properly cascading deletions
I'm working on converting the Ents SaaS Next.js Starter ( https://www.convex.dev/templates/ents-saas-starter ) away from Ents, because other than Ents it has everything I wanted. To do this I was reading about Ents, and came across this article talking about the challenges of deletion: https://stack.convex.dev/ents#cascading-deletes-soft-deletion-and-scheduled-deletion . It says:
This makes deletion in general more challenging though. You can easily have a scenario where a document’s ID is stored in 1000s or even more other documents. Deleting all of these documents in a single mutation, which is within a single transaction, is simply impossible, as it would require a long-lived transaction, grinding the whole database to a halt (something Convex does not allow, instead failing the mutation).
So in conventional Convex, what's the suggested way to cascade a delete? I would prefer my app to not fail at deleting a workspace only when it has a lot of content in it. It'd be great to have an example exactly like the ents-saas-starter that doesn't use Ents, but that may be too much to ask. Thank you, -Jon
3 replies