Oliver Rice
Oliver Rice
No progress yet but coming soon There are 3 features remaining that I think are required to hit minimal feature-completeness - globally unique id / select 1 record - views...
Would love some feedback on this thought: One concern we've had with views is that they take on the role of the creator vs the role of the query-er, which...
Here's an option for reflecting composites for folks who don't mind janky solutions ```sql WITH types AS ( SELECT n.nspname, pg_catalog.format_type ( t.oid, NULL ) AS obj_name, CASE WHEN t.typrelid...
the error would show up intermittently but all seems to be working now, thanks! I'll close this for now and re-open if it reappears
Sure, I have similar concerns about `distinct on` as the convo about https://github.com/supabase/pg_graphql/issues/193 TL;DR is that `distinct on` makes for expensive queries that are difficult to index. The concept of...
> Add support for default arguments this is done, right? > Add support for UDFs with unnamed arguments (imo) this one can be skipped > Add support for overloaded functions....
current hold up on this is that we want to log the graphql queries at `LOG` level (which is just `log!("graphql {statement}");` from pgrx prelude), but only if the `log_statement`...
I'd rather not do that if we can avoid it. for now I'll add debug level logging since that isn't impacted
yeah the concern was efficiency. adding to the context is a good idea, I'll check that out