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
It looks like ordering_aliases has moved out of the Query object in db/models/sql/query.py into the SQLCompiler object in db/models/sql/compiler.py, as of django/django@2f35c6f.
As a result, the line in johnny/cache.py referencing cls.query.ordering_aliases fail with an AttributeError.
I'm not entirely sure how easy this is to fix. It looks like cls refers to SQLCompiler and so now has an ordering_aliases property, but I don't know enough about these parts of Django and johnny-cache to confirm that swapping out cls.query.ordering_aliases for cls.ordering_aliases is a viable solution. But it seems to work.
The text was updated successfully, but these errors were encountered:
It looks like
ordering_aliases
has moved out of theQuery
object indb/models/sql/query.py
into theSQLCompiler
object indb/models/sql/compiler.py
, as of django/django@2f35c6f.As a result, the line in
johnny/cache.py
referencingcls.query.ordering_aliases
fail with anAttributeError
.I'm not entirely sure how easy this is to fix. It looks like
cls
refers toSQLCompiler
and so now has anordering_aliases
property, but I don't know enough about these parts of Django and johnny-cache to confirm that swapping outcls.query.ordering_aliases
forcls.ordering_aliases
is a viable solution. But it seems to work.The text was updated successfully, but these errors were encountered: