ISTS() using
> any of the currently released versions of Django.
>
> Cheers,
> Simon
>
> [0]
> https://github.com/django/django/commit/1ca825e4dc186da2b93292b5c848a3e5445968d7
> [1] https://github.com/django/django/pull/8119
> [2] https://code.djangoproject.com/ticket/
payment (cost=0.00..42747797.33 rows=4772627 width=4)
Filter: (NOT (SubPlan 1))
SubPlan 1
-> Index Only Scan using record_payment_id_058ca67f on
leumicard_record u0 (cost=0.42..8.47 rows=2 width=0)
Index Cond: (payment_id = payment.id)
My questions are:
*- Am I d
's data for each year
> - providing links for all possible months or days within a given year or
> month respectively.
>
> While that optimization is very related to the one you're proposing, I
> believe they're independent, you don't need to do both at once.
t likely improve performace of large list views with
date_heirarchy.
- The custom filter is applied after the ListFilters so projects that
implemented their own filters on date hierarchy fields will not be effected.
Please let me know what you think and if there are other things I haven't