Yeah classic relational database textbook stuff
Yeah classic relational database textbook stuff
15 Replies
Yeah. You want as few bugs as possible on a users table. Especially in the remote work, AI era
My background is in frontend so a lot of this knowledge is new to me, thanks for the education :)
One modification : there’s essentially never a single table for “all” business logic.
I think it’s worthwhile to study many “entity relationship diagrams” for common use cases. I think you can find many public ones for common use cases like CRM
Thank you!
Unrelated question: any best practices in Convex or examples you can point to for generating unique, human-readable slugs for rows?
There’s probably a library for that. You can shamelessly copy the adverb-animal, e.g. leaping-whale, convention that convex projects and Neon databases use
There’s some risk though. My production project’s animal isn’t very flattering haha
believe it or not, that's even after heavily trimming a lot of the least flattering adjective/animal combinations 🙂
the universe is always telling me things through those names
fully locked and loaded with Convex Auth. all functions fully audited and secured
Note to self: just implement auth / auth patterns from the start next time ;P
Hi, we're deploying Convex to Vercel and we're following the guide from Convex website, but the Vercel deployment keeps giving an error where it does not recognize that there a CONVEX_DEPLOY_KEY. The option to uncheck everything except the production environment is also missing from Vercel. I'm following the guide in here:https://docs.convex.dev/production/hosting/vercel
It would be great to get some pointers on how to resolve this. Thank you team!
Using Convex with Vercel | Convex Developer Hub
Host your frontend on Vercel and your backend on Convex.
would you recommend investing in writing optimistic updates at the moment or will everything get significantly overhauled and result in mostly duplicate work?
I have no idea where my brain was at when I wrote that. What I actually created is a drip campaign for SMS, not email. I'm writing up a quick outline for #show-and-tell in case anyone is interested in the setup.
If you're interested in really pervasive optimistic behavior, I would wait
this will overhaul current optimistic APIs with something better. so you'd probably find you did some wasted work
Is there a working example of doing auth (OAuth2) with Svelte or just plain ol' JS? Thanks in advance.
How should we be handling server side validation when using the convex useAuthActions signIn & signUp flow? I see the zod recommendation in the docs and I'm using zod on client side but I'm not sure where that should be done server side.
do you mean in terms of protecting your functions?
no, form validation for example to enforce password difficulty rules