The repository or configuration that created this release differ from a previous release. View details.
This release is a pre-release and may not be stable for production use.
MetaTables
MetaTables is a Python client and API for describing, registering, querying, and updating database tables through a governed catalog.
Its PyPI distribution is mainsequence-metatable; imports and the command are
named metatables. See publishing for the
release process and the current published SDK prerequisite.
The Python client provides SQLAlchemy table definitions, application-table
migrations, query objects, time-index readers and update processes,
and the metatables command. The MetaTables API stores table identities,
contracts, permissions, and update history, and executes authorized operations on
physical databases.
A catalog record describes a table; the table's rows live in its DataSource. The Main Sequence SDK supplies platform authentication, identity, repository context, and platform Secrets. MetaTables owns its table behavior and storage adapters. Local development runs the same API with one SQLite database for system metadata and table rows. Initialize it explicitly through Settings; startup never runs Alembic.
Start here
- Install and connect, including the complete local CLI workflow.
- Understand the concepts and identity and scope.
- Understand the security model: administration, roles on namespaces and tables, and implementation status.
- Follow the market-data tutorial with its complete examples folder.
- Define and migrate managed tables.
- Register existing tables.
- Manage DataSources: PostgreSQL, MySQL and MSSQL configuration, driver setup, examples and current operation limits.
- Build an updater or read an existing time-index table.
- Run the API locally or operate a hosted API.
The documentation index separates client, API, operations, and contributor guides. The capability reference records implemented and unavailable operations, including inherited methods and CLI commands. Runnable guide assets live in examples.
Client skills
Copy the installed client's skills into a consuming application explicitly:
metatables copy-metatables-skills --path /path/to/application
The local development skill guides application work through local SQLite setup, verified test writes, and an explicit switch back to the intended environment. The other skills cover table contracts, application migrations and producers.
The command uses the Main Sequence SDK helper, writes to
.agents/skills/metatables/, and records the client version. It works without
login or an API. Use --dry-run to preview the copy, or put global --json before
the command for structured output. See installation
for refresh behavior and the bundled references.
Development
Python 3.13 or newer is required. The package selects the published compatible SDK:
python -m pip install -e '.[dev,docs]'
python -m metatables.sdk_compat
python -m pytest -q
python -m scripts.check_project
mkdocs build --strict
Physical PostgreSQL checks use explicitly configured disposable databases; see testing. No separate frontend is needed to use the Python client or run the API.
License
MetaTables is licensed under the MIT License. See LICENSE for the complete terms.
1 maintainer
Metadata
1 maintainer
Release files for mainsequence-metatable 0.1.51.dev80
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mainsequence_metatable-0.1.51.dev80.tar.gz | 1.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mainsequence_metatable-0.1.51.dev80-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 MB
Release files / mainsequence_metatable-0.1.51.dev80.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | mainsequence_metatable-0.1.51.dev80.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7676b83f73d1df7461f3203bab9669a03a5640c31d650a27775574ebe907f6e
|
|
BLAKE2b-256 checksum How to use checksums |
7a86dd9fd41385981d08315ce695561688c08d37adb8f7d148375e970ee854b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / mainsequence_metatable-0.1.51.dev80-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | mainsequence_metatable-0.1.51.dev80-py3-none-any.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00a50847a8841b6167cd1164f93454ca028d9f34d53cf3e3bd552046663cdff1
|
|
BLAKE2b-256 checksum How to use checksums |
718c730f34f2e15a97cf8b7598aa442b5ff1742e245bed6d5de56e4fc3a6d28b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for mainsequence-metatable 0.1.51.dev80
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Configuration
- Removed 0.1.50 publish-to-pypi.yml
- Added 0.1.51.dev80 publish-dev-to-pypi.yml
Attestation for mainsequence_metatable-0.1.51.dev80.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.
