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
@loopback/sequelize is meant to be used with SQL dialects, this option being only supported by LoopBack in its memory and MongoDB connectors is not expected to work correctly.
Please use ilike or regexp operator instead depending on your needs.
@shubhamp-sf That’s true but the existing connector doesn’t throw an exception even if it is unused by the underlying MySQL connector. I was thinking for backwards compatibility / migration purposes it might be helpful if it was a no-op.
Describe the bug
This section of the code throws an exception if the "where" filter includes an "options" key:
loopback-next/extensions/sequelize/src/sequelize/sequelize.repository.base.ts
Line 604 in 96b9a56
Example filter that will throw an exception:
References:
Logs
No response
Additional information
No response
Reproduction
N/A
The text was updated successfully, but these errors were encountered: