date_hierarchy doesn't support GenerateField with output_field set to DateTimeField or DateField

[john-parton]

If you have a GeneratedField with output_field set to DateField or DateTimeField, you cannot use it in the admin as a date_hierarchy because of a check. If you skip the check, it actually works just fine in my testing. I believe this the check could be adjusted to account for this.

# models.py
class TestModel(models.Model):
    date_range = DateTimeRangeField(_("Date range"))
    start_date = models.GeneratedField(
        expression=Lower("date_range"),
        output_field=models.DateTimeField(),
        db_persist=True,
    )
    
  

# admin.py
class TestAdmin(admin.ModelAdmin):
    date_hierarchy = "start_date"

    # Skipping checks actually makes this work exactly correctly
    def check(self, *args, **kwargs):
        return ()

I'll see if I can whip up a patch.

[john-parton]

Initial patch here: ​https://github.com/django/django/pull/18407

No docs or tests yet.

[Claude Paroz]

Waiting for a final OK from Simon.

[Sarah Boyce <42296566+sarahboyce@…>]

In 7f8d8397:

Fixed #35628 -- Allowed compatible GeneratedFields for ModelAdmin.date_hierarchy.

[Sarah Boyce <42296566+sarahboyce@…>]

In 88ebcb1:

[5.1.x] Fixed #35628 -- Allowed compatible GeneratedFields for ModelAdmin.date_hierarchy.

Backport of 7f8d839722b72aeb3ec5a4278ae57c18283acacd from main.

[Sarah Boyce <42296566+sarahboyce@…>]

In c822ad6:

[5.0.x] Fixed #35628 -- Allowed compatible GeneratedFields for ModelAdmin.date_hierarchy.

Backport of 7f8d839722b72aeb3ec5a4278ae57c18283acacd from main.