What happens to my existing per-project SQLite databases after updating to v5.1.0?

They are automatically consolidated into a single shared database at ~/.config/sqlew/sqlew-shared.db. The original files are renamed to sqlew.db.migrated as a backup.

Will the migration affect databases with explicitly configured paths?

No. If your project's .sqlew/config.toml explicitly sets the database name, that database is excluded from automatic consolidation and continues to work as before.

Does sqlew still work with git worktree after this update?

Yes, and much better. The unified database means all worktrees sharing the same git repository automatically access the same knowledge base without any config changes.

Where is the global config stored after v5.1.0?

The global config is now stored at ~/.config/sqlew/config.toml, following the XDG Base Directory specification. Existing config files are automatically moved on first launch.

How do I revert to the old per-project database setup?

Rename .sqlew/sqlew.db.migrated back to .sqlew/sqlew.db and add [database] name = ".sqlew/sqlew.db" to your project's .sqlew/config.toml.

sqlew v5.1.0: Unified SQLite Database and XDG-Compliant Global Config

sqlew v5.1.0 is out. This release consolidates SQLite databases into a single shared file under the user's home directory, enabling seamless knowledge sharing across git worktrees. It also migrates the global config to an XDG Base Directory-compliant path.

What Changed

Unified SQLite Database

Starting with v5.1.0, the SQLite database is stored in a shared location under the user's home directory.

~/.config/sqlew/sqlew-shared.db

sqlew identifies data by project name and git repository information, so multiple projects coexist safely within a single database file. When working in a git worktree branch, knowledge from the same repository is immediately accessible — no config changes required.

XDG-Compliant Global Config

The global config file has moved to an XDG Base Directory-compliant path.

~/.config/sqlew/config.toml

API key files for the SaaS backend are also stored under this directory. Existing config and API key files are automatically migrated to the new path when sqlew starts, so no manual action is needed in most cases.

If you have custom settings such as a modified default DB connection, verify that your paths have been correctly carried over after the migration.

How to Update

If you installed sqlew globally via npm, run:

npm update -g sqlew

After updating, launching sqlew will automatically:

Consolidate per-project SQLite databases into sqlew-shared.db
Move legacy config and API key files to the XDG-compliant path

Migration Notes

Explicitly Configured Databases Are Not Merged

If a project's .sqlew/config.toml explicitly sets [database].name, that database is excluded from automatic consolidation. This preserves intentional setups such as team-shared databases.

Backup of Original Databases

After consolidation, the original database file in each project is renamed to .sqlew/sqlew.db.migrated. If you need to revert — for example, to restore a team-shared database — follow these steps:

Rename .sqlew/sqlew.db.migrated back to .sqlew/sqlew.db
Add the following to .sqlew/config.toml:

[database]
name = ".sqlew/sqlew.db"

Project-Level Config Still Takes Priority

The global config serves as the default, but if a project has its own .sqlew/config.toml, that config takes precedence. This allows per-project DB connection switching and other customizations.

Summary

The v5.1.0 changes are a quality-of-life upgrade for everyday sqlew usage. For developers who rely on git worktree, the reduction in configuration overhead is significant. Try it now with npm update -g sqlew.