A Principled Approach to Querying Data – A Type-Safe Search DSL
claudiu-ivan.com
A Principled Approach to Querying Data – A Type-Safe Search DSL
1–10 of 22 posts
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#2Looks good.
For a more database specific, type-safe, data querying solution, I like to use https://kysely.dev
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#3Seems a lot like FSharp Type Providers? Is that a good analogy?
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#4Looks good. For a more database specific, type-safe, data querying solution, I like to use https://kysely.dev
[deleted]
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#5[deleted]
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#6Looks good. For a more database specific, type-safe, data querying solution, I like to use https://kysely.dev
I am using both prisma and kysely in the same codebase with a great success. The db schema is driven by SQL, not prisma. It is then introspected by both kysely and prisma, prisma is used in 95% of the places while kysely is used whenever performance is critical or when prisma doesn't support the SQL features we need.
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#7The same should apply to configuration, we have prisma for sql, we should have something like this for JSONs, like https://typeconf.dev (I’m one of the founders)
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#8The same should apply to configuration, we have prisma for sql, we should have something like this for JSONs, like https://typeconf.dev (I’m one of the founders)
[deleted]
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#9> Users expect near-native responsiveness, even when offline
Do they? I think users are amazed if anything works without internet with modern applications.
Re: A Principled Approach to Querying Data – A Type-Safe Search DSL
#10Looks good. For a more database specific, type-safe, data querying solution, I like to use https://kysely.dev
I am using both prisma and kysely in the same codebase with a great success. The db schema is driven by SQL, not prisma. It is then introspected by both kysely and prisma, prisma is used in 95% of the places while kysely is used whenever performance is critical or when prisma doesn't support the SQL features we need.
any underlying negative consequences on letting prisma schema handle the underlynig model/migrations
I found out about stackzen yesterday, really like the RBAC/ABAC backed up into the models/codegen stuff, been thinking about just using that for our custom logic and maybe add RLS pg a la supabase but also codegen from the same .zmodel from zenstack model that generates prisma models/migrations have it generate RLS sql migrations code
thoughts??
also maybe postgres views to handle field/attribute level security since rows is mostly about whole columns
main goal is to secure the data at all the levels of the stack from db to api to app so there's no footguns in the future where someone with a pg user or modifying our clients can see data they shouldn't etc