Open Wouter125 opened 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is the workaround in the description the recommended solution? I have run into this as well. Here's the GraphQL query we are trying to execute:
roles(where: { users: { have: { id: { equalTo: $userId } } } }) {
edges {
node {
name
users {
edges {
node {
username
}
}
}
}
}
}
And it results in this message from the server:
{
"errors": [
{
"message": "error: column \"users\" does not exist",
"locations": [{ "line": 19, "column": 3 }],
"path": ["roles"],
"extensions": { "code": 1 }
}
],
"data": null
}
EDIT: Similar operating environment as the original post, using PostgreSQL running in AWS RDS and parse-server
v4.5.0
@cjbland would you be willed to help fixing this bug?
Sure, I'll take a stab at it.
Issue Description
I set up a Postgres instance with Parse and GraphQL. If I run a GraphQL query against my db that contains a relation, the relation is being resolved as a column instead of a relation causing a crash.
Steps to reproduce
Expected Results
I would expect to get an empty set of data since we have a clean Database.
Actual Outcome
Instead users is being resolved as a column and not a relation causing the following error;
Environment Setup
Server
Database
Logs/Trace
With Verbose on this is all I get;
Aditional
It does work if I create the user column myself through PGAdmin. Then it correctly resolves the relation instead of the column. So it's either inside the schema or the resolver.