This ORM uses a very minimalistic approach. The general idea is that the database schema is defined elsewhere (writing the SQL directly, or using some specialized software), and all the transactions are implemented either as methods in sub-classes of “Database”, or as stored procedures.
This ORM allows you to very easily: (1) implement complex database transactions, (2) call stored procedures, (3) do simple queries. For complex queries you should use database views and stored procedures that return tables.
Metadata
Release files for CuriousORM 1.0.2
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 | |
|---|---|---|---|---|
| CuriousORM-1.0.2.tar.gz | 6.5 kB | Without provenance | Details |
Release files / CuriousORM-1.0.2.tar.gz
| Download URL | CuriousORM-1.0.2.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c27169dcd2b725f8c038d6a6bdd8cb4f37450d1d9fac5357dc514a5a8392d64a
|
|
BLAKE2b-256 checksum How to use checksums |
eca5f526016b26e04705b897c489a111ffdda45e307cc0ff327f47d008d53618
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for CuriousORM 1.0.2
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.