What it is
tables.
A venture edits [tables] in venture.toml and redeploys without a rebuild, so the schema is a runtime value: rows are dynamic values checked by an interpreter reading that value, not typed structs fixed at compile time. The schema type is a small purpose-built enum rather than JSON Schema, which says nothing about the SQLite and Postgres mapping; a JSON Schema view is emitted from it instead.
Note
A crate rather than a module: it has no routes of its own. The typed row API over a declared table is cratefield-tables-api, which is internal for now.
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core
Other
- updated the following local packages: cratefield-core
2 earlier versions 0.3.0 to 0.4.0
Changed
- Breaking: requires
cratefield-core0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).
Other
- updated the following local packages: cratefield-core
- Breaking: requires
One declaration, and every artifact derived from it.