This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 73
Semantics of how the or
operator should be used
#2009
Comments
Automatically generated comment to notify maintainers |
Thanks for highlighting this one @machi1990 - this is in fact a bug and should be actioned ASAP. |
Going to start this. |
Thanks @craicoverflow |
2 tasks
2 tasks
This should be re-opened, as I believe there are still bugs in the knex query builder. We are experiencing that this simply does not work as expected for Postgres + Knex for any and/or query on the same field. Example:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@graphback/runtime-mongodb
,@graphback/runtime-knex
When combined with the
root
query operators, theor
operator evaluates tofind X where <root query conditions> OR <or conditions>
. Take the example below. This outputs the following pseudo-query in both Postgres and MongoDB:find Blogs where name is "blog3" or name is "blog3"
or condition3....Upon initial raising of this as being potentially incorrect by @machi1990 and then checking out alternative libraries (namely AWS AppSync), the query above should output:
find Blogs where name is "blog3" and (name is "blog3" || condition2 || condition 3)...
The text was updated successfully, but these errors were encountered: