Oliver Rice

using table inheritance for type unions is a very interesting idea @bryanmylee table inheritance is pretty out-of-fashion and I recall being told that its no longer recommended. I'll ask the...

IIRC its a bunch of little things - can negatively impact query performance when there are lots of child tables - constraints/indexes aren't inherited - can't cascade alter statements to...

@aaronbond its still a ways out for now we're rapidly getting to the point where request/response oriented pg_graphql *core* functionality is complete. That doesn't mean expanding the schema will stop,...

@rlee1990 if this is something you need I'd recommend checking out [realtime](https://supabase.com/docs/guides/realtime) or an externally hosted GraphQL option There are several paths forward for this feature but all of them...

@kav `not in` support sounds reasonable to me. I opened a new issue #311 to track it separately so we can keep this one narrowly focused on `String`-like types ---...

No movement yet but I'm aware that this is high interest feature The only higher priority is user defined mutations via SQL functions FYI: Everyone is currently finalizing deliverables for...

> Interested in this one. Is there any workaround now like database views or whatever? unfortunately, there isn't currently a workaround for filtering parents based on children

none yet, but we've identified nested inserts (which requires upsert support to work well) as the next big project we're tackling in pg_graphql so you should start to see movement...

You could - write a [function](https://supabase.github.io/pg_graphql/functions/) that performs the filter ahead of time - use two requests / filter on the client - use a [computed field](https://supabase.github.io/pg_graphql/computed_fields/) if you're always...

this issue was resolved by #221 and is live on the supabase platform and docker images