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
Issue type:
[ ] question [x] bug report [ ] feature request [ ] documentation issue
Database system/driver:
[ ] cordova [ ] mongodb [ ] mssql [ ] mysql / mariadb [ ] oracle [ ] postgres [ ] cockroachdb [ ] sqlite [ ] sqljs [ ] react-native [ ] expo
cordova
mongodb
mssql
mysql
mariadb
oracle
postgres
cockroachdb
sqlite
sqljs
react-native
expo
TypeORM version:
[x] latest [ ] @next [ ] 0.x.x (or put your version here)
latest
@next
0.x.x
Steps to reproduce or a small repository showing the problem:
Right now if you have an entity A with a relation to B, this will silently drop that part of the where clause and not throw any errors.
repo.find({ where: { bId: 123 } }
It works if you do
repo.find({ where: { b: { id: 123 } } }
However, this is an easy mistake to make.
I think TypeORM should throw warnings for unknown fields in the where clause and/or update the typings to not allow unknown fields.
The text was updated successfully, but these errors were encountered:
Duplicate of #3416
Sorry, something went wrong.
No branches or pull requests
Issue type:
[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[ ]
mysql
/mariadb
[ ]
oracle
[ ]
postgres
[ ]
cockroachdb
[ ]
sqlite
[ ]
sqljs
[ ]
react-native
[ ]
expo
TypeORM version:
[x]
latest
[ ]
@next
[ ]
0.x.x
(or put your version here)Steps to reproduce or a small repository showing the problem:
Right now if you have an entity A with a relation to B, this will silently drop that part of the where clause and not throw any errors.
It works if you do
However, this is an easy mistake to make.
I think TypeORM should throw warnings for unknown fields in the where clause and/or update the typings to not allow unknown fields.
The text was updated successfully, but these errors were encountered: