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
Users can already use the direct connection with their Postgresql instance on Supabase, however, an additional PoC feature could be to implement an Ecto.Adapter for PostgREST.
Also, we possibly could generate schemas/relations/migrations and also some basic CRUD functions based on the schema of the database instance of supabase.
Finally, maybe would be interestig to implement DSL that is independent from ecto to interact directly with PostgREST
Piorities:
generate ecto schemas based on supabase database schema
create an Ecto.Adapter (?)
implement DSL (?)
(?) - only a PoC for now
The text was updated successfully, but these errors were encountered:
zoedsoupe
changed the title
Integrate with PostgREST supabase interface
[PostgREST] Integrate with Ecto
Nov 20, 2023
It would be v nice to have the RLS context set for you on all Ecto queries tho.
This way if you use a Supabase HTTP API or direct connections via Ecto you can ensure users always only see the data they should see based on your RLS policies.
zoedsoupe
transferred this issue from supabase-community/supabase-ex
Dec 9, 2024
Users can already use the direct connection with their Postgresql instance on Supabase, however, an additional PoC feature could be to implement an
Ecto.Adapter
for PostgREST.Also, we possibly could generate schemas/relations/migrations and also some basic CRUD functions based on the schema of the database instance of supabase.
Finally, maybe would be interestig to implement DSL that is independent from ecto to interact directly with PostgREST
Piorities:
Ecto.Adapter
(?)The text was updated successfully, but these errors were encountered: