GraphQL Queries failing for one-to-many relationship. | amplication | Page 1

onyx carbonBOT Jun 11, 2023, 12:21 AM

#

special_sauce#9414 has been warned

Reason: Duplicated text

#

GG @worthy roost, you just advanced to level 1!

worthy roost Jun 11, 2023, 12:22 AM

#

oh that is so depressing i typed out such a big description of the issue

#

to briefly reiterate i am seeing the following error message when trying to view a user that has a one to many relationship with the character object in the admin app:

onyx carbonBOT Jun 11, 2023, 12:23 AM

#

special_sauce#9414 has been warned

Reason: Duplicated text

#

special_sauce#9414 is now unbanned

worthy roost Jun 11, 2023, 1:23 AM

#

lord have mercy it banned me

worthy roost Jun 11, 2023, 1:52 AM

#

let me use screenshots since MEE6 is super aggro

#

Here's the relational setup for character:

#

and for user:

#

setting the field in admin shows the name if a name is set for user, otherwise their uid:

#

here's the error message when the admin app attempts to fetch characters related to one user or vice versa:

maiden loom Jun 11, 2023, 4:19 AM

#

Sorry for this mess

#

We will look into the bot settings

#

Also, we will review your question and get back to you soon

lapis nebula Jun 11, 2023, 5:48 AM

#

Ahh. I made you immune to the bot. So sorry! I will change the settings of bot to something else.

maiden loom Jun 11, 2023, 5:55 AM

#

@worthy roost the error makes a lot of sense - because the character entity does not have a "user" field, you called it "owner".
it looks like an issue in the query generator.
Does you code available on a public repo we can investigate?
Other wise, could you please send a more detailed screenshot with the list of fields? (you can DM it in case you prefer to)

worthy roost Jun 11, 2023, 5:57 AM

#

Absolutely, I'll drop an ss here tomorrow since i'm not on a public repo. I can always change the field name to user rather than owner. I suspected this might actually be causing the issue but wasn't sure if foreign key name mismatches were okay or not.

onyx carbonBOT Jun 11, 2023, 5:57 AM

#

GG @worthy roost, you just advanced to level 2!

maiden loom Jun 11, 2023, 6:00 AM

#

This will probably resolve your issue, but definitely should not be THE solution. It should work with "owner".
Looking forward to seeing the screenshots. Meanwhile, we will try to reproduce the issue without it and let you know in case we made any progress.

quick hill Jun 11, 2023, 2:50 PM

#

Thanks for letting us know @worthy roost!
I opened a bug report for this; it also reproduces easily for me. We will get to it soon.
You can follow the ticket for status: https://github.com/amplication/amplication/issues/6201

GitHub

🐛 Bug Report: Setting a relation between entities not using the rem...

What happened? When you create a new entity and add a field that relates it to the user entity but do not call the new field "user" but something else (e.g. "owner"), then some ...

worthy roost Jun 11, 2023, 4:07 PM

#

this is great, thank you for your help - do you still need more screenshots since you were able to repro or are you good?

quick hill Jun 11, 2023, 4:25 PM

#

Nope, thanks a lot!
Now that we have the reproduction, we have everything we need.

#GraphQL Queries failing for one-to-many relationship.