Does the parser support `contains(field, value)` comparisons? about odata-query

[OliverHofkens]

Hey, glad you like the library, thanks!

It seems that this is a bug, specifically when using the Django backend. I've tested against both our SQLAlchemy app and Django app, and the Django test does indeed fail. Good catch!

In the case of contains however, the comparison isn't strictly necessary as contains already returns a boolean. So your example should work if you just use contains(category,'danielle hutchens') or contains(email,'danielle hutchens') or ... (without the eq true).

I'm gonna look into this, as your query is also correct and should just work.

[OliverHofkens]

Hmmm, I though I'd found a solution in db85807. Turns out it relies on new functionality only introduced in Django 4. I'll have to rethink my fix!

[al-the-x]

Happy to contribute here. For our use case, Salesforce is the client, so we don't really have control of the query that is constructed. I suppose we could inspect the AST and drop the Eq with a left-hand Call for the Call itself, if that's the issue?

[OliverHofkens]

Hey @al-the-x ,
sorry to keep you waiting for so long. I felt like I was perpetually within 5 minutes of fixing this, but things kept popping up.
#20 would fix this issue, but includes quite a big change to how Django queries are constructed (in line with new Django 4 features). I wouldn't recommend updating production software blindly, as some issues are present relating to upstream Django issues (e.g. https://code.djangoproject.com/ticket/33705).

Your fix would definitely be a good band-aid if updating is not an option!