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
// We know that it's number operator so Prisma should query number
103
151
// Note that if we get string values in DB(e.g. '100'), those values can't be filtered with number operators.
104
-
if(isNumberOperator){
105
-
prismaWhere={
152
+
returnnegatePrismaWhereClauseIfNeeded(
153
+
{
106
154
response: {
107
155
path: [mainOperand,"value"],
108
156
[`${prismaOperator}`]: secondaryOperandAsNumber,
109
157
},
110
-
};
111
-
}else{
112
-
// We know that it's not number operator but the input field might have been a number and thus stored value in DB as number.
113
-
// Also, even for input type=number we might accidentally get string value(e.g. '100'). So, let reporting do it's best job with both number and string.
114
-
prismaWhere={
158
+
},
159
+
isNegation
160
+
);
161
+
}
162
+
163
+
if(secondaryOperandAsNumber&&!isNumberOperator){
164
+
// We know that it's not number operator but the input field might have been a number and thus stored value in DB as number.
165
+
// Also, even for input type=number we might accidentally get string value(e.g. '100'). So, let reporting do it's best job with both number and string.
0 commit comments