Jose Olarte III
|
9e6597638e
|
chore(db): rename SQLite database file to notify.sqlite
Use a generic database filename for future notification-related storage, and update docs and env comments to match.
|
2026-07-27 16:53:53 +08:00 |
|
Jose Olarte III
|
06ec0f63e4
|
docs: document SQLite storage for FCM registrations
Update README and .env.example for the SQLite database location, schema overview, backup/WAL notes, and clarify that JSON data is not migrated.
|
2026-07-24 20:52:38 +08:00 |
|
Jose Olarte III
|
ddb969c26d
|
chore(db): remove obsolete JSON FCM token repository
Delete the unused JSON storage implementation now that SQLite is the sole persistence backend.
|
2026-07-24 17:57:44 +08:00 |
|
Jose Olarte III
|
e79d55fac6
|
perf(db): tighten SQLite FCM registration queries
Drop the upsert pre-read, project only needed columns, and add a (user_id, fcm_token) index for token lookups and dedupe deletes.
|
2026-07-24 17:31:23 +08:00 |
|
Jose Olarte III
|
11bd45b460
|
feat(db): switch runtime storage to SQLite repository
Point routes, scheduler, and push service at fcmTokensSqlite so the service no longer reads or writes the JSON store.
|
2026-07-23 18:55:17 +08:00 |
|
Jose Olarte III
|
5a3c22a4e3
|
feat(db): add SQLite FCM registration repository
Mirror the JSON repository API on SQLite without switching callers; clarify that SQLite is the storage backend and there is no JSON data migration.
|
2026-07-23 18:36:10 +08:00 |
|
Jose Olarte III
|
fa8ab86cdb
|
feat(db): add SQLite foundation for FCM registration storage
Introduce better-sqlite3 and a schema-init module so we can migrate off JSON storage without changing runtime behavior yet.
|
2026-07-23 17:44:27 +08:00 |
|