feat(db): add checked metadata preparation - #722
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
alignc db prepare, native schema description, exact schema/server identities, and offline whole/per-unit consumptionWhy
Q3 closes the checked/offline
pkg.dbcapability across producer, codec, native database, filesystem publication, and compiler consumer boundaries. CheckedRequired descriptors now have reproducible repository evidence instead of a dormant contract.The review cycle also closed ambient libpq target selection, cross-statement schema drift, mixed metadata generations, prepare/runtime static-option drift, logical/native parameter pairing, and zero-column Query handling.
Impact
Developers can explicitly regenerate or check SQLite/PostgreSQL metadata with
alignc db prepare. Normalcheckandbuildconsume only canonical.align-dbfiles and never contact a database. PostgreSQL preparation requires a complete URL supplied through a non-PG*environment variable and rejects ambientPG*configuration.Validation
scripts/cargo.sh test -p align_driver --test pkg_db_q3 -- --nocapture(14 passed locally; PostgreSQL native case is required, non-skippable CI)scripts/cargo.sh test -p align_driver --lib static_inputs::tests::metadata_publication_lock_closes_first_publish_and_overlap_races -- --exactscripts/cargo.sh check -p align_driver --lib --bin aligncscripts/cargo.sh clippy -p align_driver --lib --bin alignc --test pkg_db_q3 -- -D warningsscripts/pre-pr.sh ...(Q3 owner, repository PR gate, workspace lib/bin Clippy)