Closed wesharper closed 4 days ago
Reproducible Example issue_551_too_many_fields.txt
select jsonb_pretty(
graphql.resolve($$
{
barCollection {
edges {
node {
id
field1
field2
-- works
select jsonb_pretty(
graphql.resolve($$
{
getFooById(fooId: 1) {
bar {
id
field1
field2
...
-- "message": "cannot pass more than 100 arguments to a function"
select jsonb_pretty(
graphql.resolve($$
{
fooCollection {
edges {
node {
bar {
id
field1
field2
-- "message": "cannot pass more than 100 arguments to a function"
Describe the bug We have a relatively complex query for a very wide sql table from which we need almost all of the fields for our client view. To manage this, we have a query split up into 9 separate fragments, each of which specifies between 2 and 50 fields. However, when I attempt to run the query, pg_graphql spits back the following error message:
cannot pass more than 100 arguments to a function
.It appears to be similar to issue #353, but I've verified that my
pg_graphql
version includes the patch for the referenced issue. Is there indeed a 100 field limit on all queries even with the patch?To Reproduce Steps to reproduce the behavior:
bar
, which stores 140 columns.foo
, which stores its own primary key and a reference to a primary key frombar
.Expected behavior The query should execute successfully.
Versions:
Additional context Without deeper knowledge of the transpiler, I attempted to suss out issues that might be related to my own specific use-case. Here are some of the things I tried:
getRecordById
, as explained in the repro steps, rather than requesting from a collection resolver. However, when I tried the same query using the collection resolver, I encountered the same issue.