datatug / datatug-cli / 26886975278

62%

push

github

feat(sqlite): extract indexes, foreign keys and constraints (and persist them) (#141)

The sqlite schemer previously returned empty for indexes/index-columns/
constraints (they were fake MS-SQL/INFORMATION_SCHEMA stubs). Implement them
natively via PRAGMA:

- GetIndexes        -> PRAGMA index_list  (name, unique, origin, partial)
- GetIndexColumns   -> PRAGMA index_info
- GetConstraints    -> PRAGMA foreign_key_list (FOREIGN KEY) + unique-origin
                       indexes (UNIQUE). Primary keys come from column metadata,
                       so they are not re-emitted here.

The providers now live on schemaProvider (so they share the DB getter), and
the empty stub structs are removed.

To make the extracted relationships reach disk, TableModel gained PrimaryKey,
ForeignKeys, ReferencedBy, Indexes and AlternateKeys fields, and
updateSchemaModel now copies them from the scanned catalog (previously only
columns were carried into the persisted DB model).

Verified end-to-end: scanning chinook now writes, per table, the foreign keys
(e.g. Album.ArtistId -> Artist), indexes with their columns, primary key, and
reverse references. Tests: a scanDbCatalog extraction test (FK + index +
unique + referenced-by) and an extended SaveProject round-trip (PK/FK/index
survive save+load). Full module build, vet and test suite pass.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

0 of 174 new or added lines in 4 files covered. (0.0%)

5527 of 14457 relevant lines covered (38.23%)

0.45 hits per line