djfim

License

Apache License Version 2.0

Usage

a) declare concrete datamodel:

# app/models.py
from django.db import models
from djfim.models import Blob, Entity, Generation

class MyBlob(Blob):
    class Meta:
        abstract = False

class MyEntity(Entity):
    generation = models.ForeignKey('MyGeneration', on_delete=models.CASCADE, null=False)
    blob = models.ForeignKey('MyBlob', on_delete=models.CASCADE, null=False)

    class Meta:
        abstract = False

class MyGeneration(Generation):
    l_anchor = models.ForeignKey('self', on_delete=models.SET_NULL, null=True, related_name='l_subtree')
    r_anchor = models.ForeignKey('self', on_delete=models.SET_NULL, null=True, related_name='r_subtree')

    class Meta:
        abstract = False

b) migrate datamodel:

python manage.py makemigrations
pythno manage.py migrate

c) setup datamodel reference:

# project/settings.py
DJFIM = {
    'MODLE': {
        'BLOB': {
            'app_name': 'app',
            'app_label': 'MyBlob',
        },
    }
}

d) invoke management command:

python manage.py fim [action]

Metadata

Release files for djfim 0.5.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for djfim 0.5.8
File	Interpreter	ABI	Platform	Actions Reset
djfim-0.5.8-py3-none-any.whl 38.2 kB Mar 16, 2023 Without provenance	Python 3	none	any	Details for djfim-0.5.8-py3-none-any.whl

Release files / djfim-0.5.8-py3-none-any.whl

Download URL	djfim-0.5.8-py3-none-any.whl
Size	38.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`5191b75a2f57eb5f0f1fe21d1892305b4151207039107dca7f7c6e6f9249c313`
BLAKE2b-256 checksum How to use checksums	`14c79b9d23be267bf0354c42af92a9fac9442918fb89487f2ac3beb87914135b`
Upload date	Mar 16, 2023
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/4.0.0 PyPy/7.3.7`

Security for djfim 0.5.8

Report project as malware

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.