django-tables2 VS django-constance

How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models with column sorting and pagination.

The degree of reusability (Thanks to things like GenericForeignKey and the ubiquity of Django Templates and Django ORM, there are tons of reusable components like django-filter or django-tables)

In Django there is django-tables2 for example, that creates html table from database query.

(eg. "Django apps" like django-filter and django-tables2, which rely on being a slice across the ORM, controller layer, and templating engine.)

From the readthedocs tutorial, A few examples:

I don't see how Axum would enable something like django-tables2 or django-filter which has is vertically integrated with Django's ORM, routing layer, and template system.

I've used actix-web for stuff... but I'm just sick of constantly reinventing the rote boilerplate that things like django-tables2 and django-filter generate for me once I've declared whatever customizations I want.

django-tables2 - like crispy forms but for tables, abstracts away the need to render tables in a template.

Can I use django-constance to change values in Django's settings files? Specifically I'd like to control the max file size upload setting DATA_UPLOAD_MAX_MEMORY_SIZE.

django-constance - Set global values using the admin interface.

Have you come across https://github.com/jazzband/django-constance? I think this might be able to help with some of your issues. It would at least allow you to save / change settings in your app globally that would work nicely with multiple workers. I typically use this library with Redis