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
I added some additional logging, and when the query gets to queryCallback, the cond.(type) is clause.AndConditions rather than either of the 2 expected values.
The value was something like Checking clause: {[{id [3872 3877]} {username *person@domain*}]}
Looking at the previous behaviourpassing through gorm-like, it would have processed 2 seperate clauses,
cond: {id [3872 3877]} as an IN
cond: {[{username LIKE ? [%person@domain%]
So it looks like perhaps I was still relying on the old wildcard behavrious in gorm-deep-filtering, but gorm-like doesnt seem to drop in as expected?
I have a query that looks something like this
SELECT count(*) FROM
userWHERE
idIN (3872,3877) AND
username= '*person@domain*'
When updating some packages, gorm-like appears to stop working for this query.
I added some additional logging, and when the query gets to
queryCallback
, thecond.(type)
isclause.AndConditions
rather than either of the 2 expected values.The value was something like
Checking clause: {[{id [3872 3877]} {username *person@domain*}]}
Looking at the previous behaviourpassing through gorm-like, it would have processed 2 seperate clauses,
cond: {id [3872 3877]}
as anIN
cond: {[{username LIKE ? [%person@domain%]
So it looks like perhaps I was still relying on the old wildcard behavrious in
gorm-deep-filtering
, butgorm-like
doesnt seem to drop in as expected?My setup has
The text was updated successfully, but these errors were encountered: