Best way to use custom LogEntry queryset for auditlog_history_view ?

[jpmoral-cg]

Hi, AuditlogHistoryAdminMixin.auditlog_history_view queries and displays entries like so:

def auditlog_history_view(self, request, object_id, extra_context=None):
    # stuff

    log_entries = (
        LogEntry.objects.get_for_object(obj)
        .select_related("actor")
        .order_by("-timestamp")
    )

    # other stuff

What would the best way be to use a custom queryset instead, e.g. one that include entries for child objects? I'm hoping to avoid redefining auditlog_history_view in my own admin view since I only want to change the queryset.

[2ykwang]

@jpmoral-cg

Could you elaborate on your use case?
-> For example, what kind of child objects are you trying to include?

I hadn't considered adding a way to customize the queryset when I initially implemented this,
but it sounds like a good idea

[jpmoral-cg]

@2ykwang

Say for example I had the following:

class Invoice(models.Model):
    invoice_number = models.CharField()
    # other fields


class LineItem(models.Model):
    invoice = models.ForeignKey(Invoice)
    # other fields

I want to see LineItem log entries:

1. included in the Invoice audit log (right now I always want to include them, but there may be cases in the future where I would want to filter the log entries by line item only, non line item fields only, etc.)
2. only in the Invoice audit log, as users don't think of the line items separate from their invoices

So the queryset will be something like:

LogEntry.objects.filter(
    Q(**invoice_filter) | Q(**line_item_filter)
).select_related("actor").order_by("-timestamp")

I hope that makes sense.

[jpmoral-cg]

I tried a custom queryset just by editing the code, the unintended consequence is that it can be confusing if I don't also customise the template to differentiate between entries for each model.