django-denorm-iplweb is a Django application to provide automatic management of denormalized database fields.
This is a fork of original package, that went by name of django-denorm . This fork should bring original package to the latest Django/Python versions. Also, support for pretty much anything that is not PostgreSQL was dropped.
Supported versions:
Django 5.2 LTS |
Django 6.0 |
Django 6.1 |
|
|---|---|---|---|
Python 3.10 |
✅ |
❌ |
❌ |
Python 3.11 |
✅ |
❌ |
❌ |
Python 3.12 |
✅ |
✅ |
✅ |
Python 3.13 |
✅ |
✅ |
✅ |
Licensed under the BSD 3-Clause license.
Requires Celery.
Reasons for this fork being PostgreSQL-only:
lack of resources for maintaning other backends,
usage of LISTEN/NOTIFY mechanisms, available in PostgreSQL,
many more improvements, for example the ability to run multiple instances of cache rebuilder (see docs)
Patches welcome!
Deferring computation
Fields declared with @denormalized are computed synchronously when their model is saved. To skip that for selected fields, e.g. while the Django admin saves a parent object before its inlines, wrap the writes in denorm.deferred(). The fields are then left untouched on UPDATE (or set to their default on INSERT) and marked dirty for flush() on block exit:
import denorm
from django.db import transaction
with transaction.atomic(), denorm.deferred("app.Article.summary"):
article.save()
for section in sections:
section.save()
See the tutorial (“Deferring the computation”) for details and limitations.
Dirty instances view
The package ships with an optional view that displays the current number of DirtyInstance rows grouped by content type — useful for monitoring the denormalization queue from a browser instead of running ./manage.py denorm_show_dirtyinstances_count over SSH.
Wire it into your project’s URLConf:
# urls.py
from django.urls import include, path
urlpatterns = [
...
path("denorm/", include("denorm.urls")),
]
The view is then reachable at /denorm/dirty-instances/ and via reverse("denorm:dirty_instances_count").
Access policy is controlled by the DENORM_DIRTY_INSTANCES_VIEW_ACCESS setting (default: "staff"):
"staff" — only users with is_staff=True (uses staff_member_required).
"authenticated" — any logged-in user (uses login_required).
"public" — no access control. Only enable this behind your own network-level protection; the page leaks model names from your project.
Example:
# settings.py DENORM_DIRTY_INSTANCES_VIEW_ACCESS = "authenticated"
Documentation is available from http://django-denorm-iplweb.github.io/django-denorm-iplweb/
Issues can be reported at http://github.com/mpasternak/django-denorm-iplweb/issues
Metadata
Release files for django-denorm-iplweb 1.15.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_denorm_iplweb-1.15.0.tar.gz | 107.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_denorm_iplweb-1.15.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 192.9 kB
Release files / django_denorm_iplweb-1.15.0.tar.gz
| Download URL | django_denorm_iplweb-1.15.0.tar.gz |
|---|---|
| Size | 107.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af02ab2dc3b4d3d095492f5edc8f5ec141b74917f2e3c837a9cc172dd2b72df2
|
|
BLAKE2b-256 checksum How to use checksums |
3a3005e464e6c014eb369d7f707d0eb8bd2018b558766c9ceb5e48a2498c7d2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / django_denorm_iplweb-1.15.0-py3-none-any.whl
| Download URL | django_denorm_iplweb-1.15.0-py3-none-any.whl |
|---|---|
| Size | 85.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9563fc338ff6de5ec4927bdfbef987630001b95cfecd92261765091fb47955dd
|
|
BLAKE2b-256 checksum How to use checksums |
cde80650b3625fe2eb3a53193c3ef7b2bb6038607d4cf39cedbb56bc80ba7795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for django-denorm-iplweb 1.15.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.