Hidden nature of `.sqlite-records.db` is confusing #124

New issue

Closed

opened 2025-09-03 07:16:20 +00:00 by mih · 2 comments

mih commented

2025-09-03 07:16:20 +00:00

(Migrated from github.com)

With a sqlite backend, no other file than the DB file is necessary. This means that there is likely gonna be a directory with just that one hidden file server-side.

This seems unnecessary and confused me multiple times already.

With a sqlite backend, no other file than the DB file is necessary. This means that there is likely gonna be a directory with just that one hidden file server-side. This seems unnecessary and confused me multiple times already.

christian-monch commented

2025-09-05 07:05:49 +00:00

(Migrated from github.com)

I see your point. The .-prefix was chosen to prevent clashes between class names and the SQL database name, and record-dir-index already used it.

We can use another prefix, e.g. _, or __. WDYT?

As migration strategy we could add __sqlite-records.db-links to existing stores and use __sqlite-records.db for newly created stores.

I see your point. The `.`-prefix was chosen to prevent clashes between class names and the SQL database name, and record-dir-index already used it. We can use another prefix, e.g. `_`, or `__`. WDYT? As migration strategy we could add `__sqlite-records.db`-links to existing stores and use `__sqlite-records.db` for newly created stores.

christian-monch commented

2025-09-30 07:45:09 +00:00

(Migrated from github.com)

Version 4.2.0 introduces __sqlite-records.db as the name for the SQL records database. Stores that use the old name, i.e., .sqlite-records.db, will be moved to the new name. The following mechanism is used to move the database to the new name:

Create a backup copy of .sqlite-records.db in .sqlite-records.db.backup
Move .sqlite-records.db to __sqlite-records.db

Version 4.2.0 introduces `__sqlite-records.db` as the name for the SQL records database. Stores that use the old name, i.e., `.sqlite-records.db`, will be moved to the new name. The following mechanism is used to move the database to the new name: 1. Create a backup copy of `.sqlite-records.db` in `.sqlite-records.db.backup` 2. Move `.sqlite-records.db` to `__sqlite-records.db`