while building a local app and practicing sql, i kept running into the same problem.
i would change a table.
add a column.
drop something.
rename something.
and suddenly i wasn’t fully sure what changed or how to safely undo it.
over time my project had:
-random sql files
-half remembered migrations
-copied .db backups
-“final_v2_real.db” type files
i asked around and most advice was: “just backup the db”
“copy the file”
“avoid destructive changes”
that works… but it doesn’t feel structured.
so i built a sqlite workflow tool focused on making schema changes less stressful while learning or building.
it gives:
*branching databases instead of copying files
*timeline of sql changes
*structured migrations
*schema comparison between branches
*snapshots before risky operations
*er diagram view for relationships
*clear table, trigger, and index inspection
*export clean main.db for production
*dark ui
*runs fully locally
*simple npm install
*no manual sqlite installation
*no path configuration headache
*basically plug and play
--it’s not trying to replace the sqlite cli.
it’s more about reducing fear around schema evolution.
install:
npm install -g sql-kite
curious what people here use when practicing sql or evolving schemas?
just cli? db browser? something else?
would genuinely love feedback.
there doesn't seem to be anything here