django-compositepk
A Django application that provides a CompositePKModel, allowing for basic retrieval and saving of models with composite keys.
It is limited to the above tasks, and any use of the model past this is not guaranteed to work.
Example usage
A model with composite PK should look something like this:
from composite_pk import composite
class Lot(composite.CompositePKModel):
auction = models.ForeignKey(Auction, primary_key=True)
lot_number = models.IntegerField(primary_key=True)
objects = composite.CompositePKManager()
So it must:
subclass the CompositePKModel,
have two or more fields which set the primary_key attribute to True, and
use the CompositePKManager as the initial manager.
1 maintainer
Metadata
1 maintainer
Release files for django-compositepk 1.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 | Actions |
|---|---|---|---|---|
| django-compositepk-1.0.tar.gz | 3.4 kB | Without provenance | Details for django-compositepk-1.0.tar.gz |
Release files / django-compositepk-1.0.tar.gz
| Download URL | django-compositepk-1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87167e6548d11124c11089cb515b555d2c80290df7c14213e8732e4654dc916a
|
|
BLAKE2b-256 checksum How to use checksums |
3f722ba1ac5d793e9904e009488d9fb0a8494a115bedf14a0a2eacc2a804bcb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-compositepk 1.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.
