SQLite parses and stores foreign key constraints, but does not enforce them. The simple solution of this problem is creating insert,update and delete triggers which mimic the enforcing behaviour of other RDBMS. sqlitefktg does just that - automatically.
Features
automatic generation of foreign key enforcing triggers based on the data fetched from the database,
may be used as a command-line tool, as well as inside your own application,
2-phase detection/generation process allows the advanced user to customize the end result.
Metadata
Release files for sqlitefktg 0.1.1
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 |
|---|---|---|---|---|
| sqlitefktg-0.1.1.tar.gz | 5.8 kB | Without provenance | Details for sqlitefktg-0.1.1.tar.gz |
Release files / sqlitefktg-0.1.1.tar.gz
| Download URL | sqlitefktg-0.1.1.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ad4dcc6be8c603872c4e2a6d3527c4a3ef125794c02336080447ba6b47cde33
|
|
BLAKE2b-256 checksum How to use checksums |
57a64a05672076cb9b8dfb79a9134a10db5e79a0404d7aff4295fe6aa5bc7e2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sqlitefktg 0.1.1
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.