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
Steps to reproduce or a small repository showing the problem:
This issue happens when I have something like:
constquery=this.createQueryBuilder('employee')// ... complex joins and stuff...query.where('task.id IN (:...ids)',{ids: [foo,bar,etc]})constresult=awaitquery.take(5).getMany()
This causes TypeORM to bahave unexpectedly, loading an empty result.
I can see in the generated query that it substitutes by :...ids with the parameters .take() uses internally.
I consider it a bug because it can frustrate a lot of unsuspecting people. Maybe I would rename it to something more obscure to the end user.
The text was updated successfully, but these errors were encountered:
cuchi
added a commit
to cuchi/typeorm
that referenced
this issue
Dec 4, 2019
* Use a leading underscore on SelectQueryBuilder internal parameters
* Add test case for issue #5174
* Fix lint issues
* Improve test for issue #5174
* Use a different prefix for the former ...ids
* Remove .only
Issue type:
[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[ ]
mysql
/mariadb
[ ]
oracle
[x]
postgres
[ ]
cockroachdb
[ ]
sqlite
[ ]
sqljs
[ ]
react-native
[ ]
expo
TypeORM version:
[ ]
latest
[ ]
@next
[x]
0.2.20
Steps to reproduce or a small repository showing the problem:
This issue happens when I have something like:
This causes TypeORM to bahave unexpectedly, loading an empty result.
I can see in the generated query that it substitutes by
:...ids
with the parameters.take()
uses internally.I consider it a bug because it can frustrate a lot of unsuspecting people. Maybe I would rename it to something more obscure to the end user.
The text was updated successfully, but these errors were encountered: