We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When doing xByRowId queries with the same constant ID, pgSelect step does not seem to correctly deduplicate
xByRowId
Setup Postgraphile v5. Add a table with the ability to do a root query to fetch a single row of that table by its row ID
create table foo (id int primary key, a text);
Set graphile.explain to true in your preset
graphile.explain
true
Execute a query in Ruru using aliases to query the same row twice. e.g.
query MyFoos { foo1: foo(id="1") { id } foo2: foo(id="1") { id } }
See the diagram of the plan is similar to the screenshot above
Please let me know if it would be useful to create a minimal repro of this. I'm happy to do so
I expect there to be a single PgSelect step in the plan
There are 2 PgSelect steps
Additional discussion in this discord thread:
https://discord.com/channels/489127045289476126/1325736426587033652/1325879877576032288
Not sure without digging into PgSelect code
The text was updated successfully, but these errors were encountered:
Likely a bug in the deduplicate method in PgSelectStep.
Sorry, something went wrong.
No branches or pull requests
Summary
When doing
xByRowId
queries with the same constant ID, pgSelect step does not seem to correctly deduplicateSteps to reproduce
Setup Postgraphile v5. Add a table with the ability to do a root query to fetch a single row of that table by its row ID
Set
graphile.explain
totrue
in your presetExecute a query in Ruru using aliases to query the same row twice. e.g.
See the diagram of the plan is similar to the screenshot above
Please let me know if it would be useful to create a minimal repro of this. I'm happy to do so
Expected results
I expect there to be a single PgSelect step in the plan
Actual results
There are 2 PgSelect steps
Additional context
Additional discussion in this discord thread:
https://discord.com/channels/489127045289476126/1325736426587033652/1325879877576032288
Possible Solution
Not sure without digging into PgSelect code
The text was updated successfully, but these errors were encountered: