Thanks for the help, I have checked those release notes, but I was not able
to identify the related change (neither subquery nor __in lookup). I wanted
to give you a deeper look into the code, but during that I managed to
isolate the issue. It seems that the '__in' lookups previously accepted
I assume you are either using a Subquery annotation that returns
multiple results or an __in lookup against a query with multiple columns.
I vaguely remember something changed in this area but it was documented
in one of the 2.0, 2.1 or 2.2 release notes.
Best,
Simon
Le mardi 23 avril 2019
Hello,
I am facing the following issue after upgrading to 2.2 from 1.11. Here is
the stack trace:
Traceback (most recent call last):
File "(...)\.env\lib\site-packages\django\db\backends\utils.py", line 84,
in _execute
return self.cursor.execute(sql, params)
File
3 matches
Mail list logo