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
I'm Querying a specific 'Student', including a many - to many relationship for companies yet dupes are not coming back for records with the same studentId, and companyId. The join table does also have a primary key with id on it.
Look at the line where I include Companies which is a belongsToMany Relationship
Unique, and constraint dont do much they were attempts, paranoid worked though. I was able to fetch deletedAt records then.
Dialect: mysql / postgres / sqlite / mssql / any Dialect version: latest Database version: 10 Sequelize version: latest Tested with latest release: yes: 4.37.3
Note :Your issue may be ignored OR closed by maintainers if it's not tested against latest version OR does not follow issue template.
If this is a real bug, and I really do appreciate the project, when do you think something like this might be touched upon? Trying to convince teamates to use this ORM.
The text was updated successfully, but these errors were encountered:
What are you doing?
I'm Querying a specific 'Student', including a many - to many relationship for companies yet dupes are not coming back for records with the same studentId, and companyId. The join table does also have a primary key with id on it.
Look at the line where I include Companies which is a belongsToMany Relationship
Unique, and constraint dont do much they were attempts, paranoid worked though. I was able to fetch deletedAt records then.
Here are my models:
What do you expect to happen?
I expect all records to return, whether they are soft deleted or not.
What is actually happening?
Only the Last record pertaining it is returned
Here is a example of two different companies a student has belonged to
Here are the records:
Dialect: mysql / postgres / sqlite / mssql / any
Dialect version: latest
Database version: 10
Sequelize version: latest
Tested with latest release: yes: 4.37.3
Note : Your issue may be ignored OR closed by maintainers if it's not tested against latest version OR does not follow issue template.
If this is a real bug, and I really do appreciate the project, when do you think something like this might be touched upon? Trying to convince teamates to use this ORM.
The text was updated successfully, but these errors were encountered: