Currently the only supported what was django-postgresql. But I’m working for some features available for all supported backends (postgresql, sqlite, mysql), as orm connection-pool and low-level cache.
If you want to know in detail what it offers for each database, check the documentation.
Documentation: http://readthedocs.org/docs/django-orm/en/latest/
Project page: http://www.niwi.be/post/project-django-orm/
Metadata
Release files for django-orm 2.0.5
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-orm-2.0.5.tar.gz | 23.3 kB | Without provenance | Details |
Release files / django-orm-2.0.5.tar.gz
| Download URL | django-orm-2.0.5.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b226077683998fde311182119a2cc163fcb6c2b17df3b05d55bf95f5d64dc62e
|
|
BLAKE2b-256 checksum How to use checksums |
2d72bd8b88251f3eb5a84ddc4e8b4d4f72aa5558aa9fc4273c9ce7c5ac8bccdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-orm 2.0.5
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.