4
Accept pure SQL on postgrest, we will be able to use other ORMS on Vercel Edge Runtime
Source: supabase/supabase#14321 · opened by @Jaaneek
Hi,
Since postgrest is a server connected straight to the database, I was wondering if making it accept an optional SQL string would be possible.
I understand that it's not possible on client due to SQL injections. I'm not asking for that.
Not only that, but I would like it to accept SQL only when a service key was provided, meaning it would be only accessible on the server.
This could be very similar to
We would be able to opt out of the bad DX that supabase-js query client gives us and use whatever ORM we want, for example kysely or drizzle are perfect for edge runtime.
The bad DX I'm talking about is mostly typesafety:
I would also appreciate the ETA on fixing the above issue
Since postgrest is a server connected straight to the database, I was wondering if making it accept an optional SQL string would be possible.
I understand that it's not possible on client due to SQL injections. I'm not asking for that.
Not only that, but I would like it to accept SQL only when a service key was provided, meaning it would be only accessible on the server.
This could be very similar to
We would be able to opt out of the bad DX that supabase-js query client gives us and use whatever ORM we want, for example kysely or drizzle are perfect for edge runtime.
The bad DX I'm talking about is mostly typesafety:
I would also appreciate the ETA on fixing the above issue
No pledges yet. Be the first to back this.
Comments
Similar requests
Custom query parameter on postgrest-js
4 votes · 0 comments
Allow configuring PostgREST pool and pooler in Supabase CLI (api.db_pool, api.use_pooler)
1 vote · 0 comments
Extend Model Support in Edge Runtime via Hugging Face’s Candle
2 votes · 0 comments
Compression Issue with ‘application/vnd.pgrst.object+json’ Content-Type in PostgREST Responses
3 votes · 0 comments
Introducing supabase to the Haskell ecosystem
9 votes · 0 comments
No comments yet.