Changes between Initial Version and Version 4 of Ticket #22128


Ignore:
Timestamp:
Feb 23, 2014, 8:25:04 PM (10 years ago)
Author:
Shai Berger
Comment:

Description corrected per comment:3.

To the point: Would this warning still be needed after #18247 is fixed? If not, it would just be documenting a bug.

Even if it were, is it really that "aggregation is not supported" or only that "comparisons against aggregates may not perform as expected"?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22128

    • Property Owner nobody removed

  • Ticket #22128 – Description

    initial v4  
    2626Therefore, any queryset instantiated by a sqlite3 backend that uses the aggregation features described in the Django documentation [https://docs.djangoproject.com/en/dev/topics/db/aggregation/ Aggregation guide] will most probably return incorrect results. The problem has been time consuming to debug, as the origin  is not immediately clear.
    2727
    28 The master ticket for this issue appears to be #21179. The duplicated #22117 was recently open, but it is expected that more will come.
     28The master ticket for this issue appears to be #18247. The duplicated #22117 was recently open, but it is expected that more will come.
    2929
    3030Therefore, I recommend that a warning message be included after the first few paragraphs of the [https://docs.djangoproject.com/en/dev/topics/db/aggregation/ Aggregation guide], that provides an explanation of the problem.
Back to Top