Oliver Rice
Oliver Rice
none yet, we'll be looking at user defined functions and views first
sure 1. yes, its definitely going to happen 2. Currently I'd it'll be in by EO Q2 but that may change depending on who get pulled into various other priorities...
Note yet but nested inserts is the next large project we're going to tackle for GraphQL and this is pre-req for that so it should start moving soon
> update mutations update mutations are already available. you can read more about them [here](https://supabase.github.io/pg_graphql/api/#update) Work on upsert support started last week. You can track in [PR](https://github.com/supabase/pg_graphql/pull/503)
The conversation about this feature hasn't happened internally yet but I expect it'll happen with an opt-out option for people concerned about performance. User defined functions and any spec inconsistencies...
yeah, I agree. we would not be able to apply filters consistently using `old_record` because it usually only includes the primary key information. but, as Tyler pointed out, we could...
great point we'll have to make it nullable when RLS is enabled
Expanding the scope on this to: - Default all fkey linked relations to to nullable when RLS is enabled - add a comment directive `@graphql({"nullable": })` on `columns` and `foreign...
thanks, I'll take a look
hi @HadiSDev > I was going the docs for Supabase GraphQL setup at https://supabase.github.io/pg_graphql/api/#insert > >Specifically the insert part as I am trying to create a mutation with multiple inserts....