Repository navigation
Closed as not planned
Labels
help wantedExtra attention is neededExtra attention is neededscope:dbDatabase driversDatabase driversstatus:acceptedApproved, plannedApproved, plannedtestsTests, CI coverage and validationTests, CI coverage and validationtype:featureNew functionalityNew functionality
Description
Summary
Add SQLite SQL generation for schema migration operations.
The migration CLI already accepts --dialect sqlite, but migration generation currently supports only MySQL.
Current behavior
The schema diff engine produces portable migration operations.
Only MySqlGenerator converts those operations into SQL.
Requesting SQLite migration generation results in an error.
Expected behavior
The DB module must generate valid SQLite up and down migration scripts for all operations currently supported by the schema diff engine.
SQLite limitations must be handled explicitly.
Scope
- Add a SQLite SQL generator.
- Generate table creation SQL.
- Generate table removal SQL.
- Generate column addition SQL.
- Handle column removal according to supported SQLite versions.
- Generate normal and unique indexes.
- Generate down migrations.
- Quote SQLite identifiers safely.
- Connect
--dialect sqliteto the generator. - Add golden tests.
- Preserve existing schema and migration APIs.
Suggested files
modules/db/include/vix/db/mig/sql/SQLiteGenerator.hppmodules/db/src/mig/sql/SQLiteGenerator.cppmodules/db/tools/migrator/MakeMigrations.cppmodules/db/tests/sqlite_generator_test.cppmodules/db/CMakeLists.txt
Acceptance criteria
-
--dialect sqlitegenerates migration files. - All currently portable schema types map to valid SQLite types.
- Index creation and removal are supported.
- Unsupported operations fail with clear diagnostics.
- Generated up and down SQL is deterministic.
- Generated migrations execute successfully against SQLite.
- MySQL generation remains unchanged.
- Existing public APIs remain compatible.
Non-goals
This issue does not include:
- PostgreSQL generation;
- full table-rebuild automation for every SQLite alteration;
- ORM migrations;
- database introspection.
Suggested labels
scope:dbtype:featuretestshelp wantedstatus:accepted
Metadata
Metadata
Assignees
Labels
help wantedExtra attention is neededExtra attention is neededscope:dbDatabase driversDatabase driversstatus:acceptedApproved, plannedApproved, plannedtestsTests, CI coverage and validationTests, CI coverage and validationtype:featureNew functionalityNew functionality
Activity
GaspardKirira commentedon Oct 30, 2026
Closing this issue as not planned as part of the gradual Vix2 legacy backlog cleanup.
This issue concerns the former
vix::dbmodule and its Vix2 implementation/API. Vix2 is no longer being actively developed. The upcoming Vix3 generation is being built with a deliberately limited scope, and the legacy DB module and its backlog are not carried forward as Vix3 commitments.This closure does not mean the reported issue was fixed or implemented. The original report and discussion remain available for historical reference, including for those still using Vix2.
Thank you for documenting the problem.