========
Database interaction utilities for the SPARC platform.
SQL Databases
-------------
Interactions to SQL databases are provided via SQLAlchemy (http://www.sqlalchemy.org/).
In addition, z3c.saconfig (https://pypi.python.org/pypi/z3c.saconfig) is
provided to allow connection configuration andintegration of SQLAlchemy in ZCA.
### Usage - SQLite memory DB connection
These steps will give you access to a SQLAlchemy session, see the SQLAlchemy
docs to understand how to interact with this object.
>>> import sparc.db
>>> from sparc.common import Configure
>>> from zope.component import getUtility
>>> from z3c.saconfig.interfaces import IEngineFactory, IScopedSession
>>> Configure((sparc.db, 'memory.zcml',))
>>> myEngine = getUtility(IEngineFactory, name="memory_engine")
>>> mySession = getUtility(IScopedSession, name="memory_session")
The above example gives access to a in-memoery SQLite instance. In practice,
you would create your own db.zcml with the appropriate connection information.
See SAConfig documentation on how to create the ZCML configu file.
sparc.db
==========
0.0.3
++++++++++++++++++
* pypi packaging update
0.0.2
++++++++++++++++++
* include zcml configuration files in packaging
0.0.1
++++++++++++++++++
* initial release
Metadata
Release files for sparc.db 0.0.3
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 |
|---|---|---|---|---|
| sparc.db-0.0.3.tar.gz | 9.1 kB | Without provenance | Details for sparc.db-0.0.3.tar.gz |
Release files / sparc.db-0.0.3.tar.gz
| Download URL | sparc.db-0.0.3.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00ac41b7e1129984e257e94df99c7e841f9977f51fc1c47b84ecb984528d8468
|
|
BLAKE2b-256 checksum How to use checksums |
f9f2bc3e1eff665c10c0d03d15c2caf89576286d909d92420237d37807d3741c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sparc.db 0.0.3
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.