You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The query worked fine, until I added the include parameter. It returns an Array of users that have a 1:1 relation to the Gym model through a foreign key in the Gym model. Including the Gym works fine with the findOne and findMany method.
This approach leads to the Promise neither resolving nor rejecting with an error.
Versions
sequelize: ^6.31.1
sequelize-typescript: ^2.1.5
typescript: ^5.0.4
Issue type
bug report
feature request
Actual behavior
The returned Promise of $get doesn't get resolved or rejected.
Expected behavior
The user should have a attribute gym that contains the gym's information if the user is related to a gym.
Steps to reproduce
Have 2 Models. Add a 1:n relation between Model A and itself. Add a 1:1 relation between Model A and B. Get all related Model A's from a specific instance of Model A using the $get method and include Model B
The text was updated successfully, but these errors were encountered:
Issue
I have tried using eager loading in combination with the $get method on a sequelize object:
The query worked fine, until I added the include parameter. It returns an Array of users that have a 1:1 relation to the Gym model through a foreign key in the Gym model. Including the Gym works fine with the findOne and findMany method.
This approach leads to the Promise neither resolving nor rejecting with an error.
Versions
Issue type
Actual behavior
The returned Promise of $get doesn't get resolved or rejected.
Expected behavior
The user should have a attribute gym that contains the gym's information if the user is related to a gym.
Steps to reproduce
Have 2 Models. Add a 1:n relation between Model A and itself. Add a 1:1 relation between Model A and B. Get all related Model A's from a specific instance of Model A using the $get method and include Model B
The text was updated successfully, but these errors were encountered: