Investigate purpose of authentication.db #212

Closed
opened 2026-02-06 19:26:42 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @sparky8251 on GitHub (Jan 6, 2019).

This is part of #42 and #422.

This one is a bit complicated. It has 2 tables and 3 indicies.

The Devices table has 3 fields:

Id which is TEXT and is the master key.
CustomName which is TEXT
Capabilities which is TEXT

The Tokens table has 11 fields:

Id which is INTEGER and is the master key.
AccessToken which is TEXT
DeviceId which is TEXT
AppName which is TEXT
AppVersion which is TEXT
DeviceName which is TEXT
UserId which is TEXT
UserName which is TEXT
IsActive which is BIT
DateCreated which is DATETIME
DateLastActivity which is DATETIME

As for the indexes, looking at my DBs layout, its apparent that the tables should be joined into one rather than splitting them up and joining them. This will require code fixes to stop the joins and just directly query the DB.

Would like confirmation on my take for this DB before proceeding. I have lacking experience with DBs.

Originally created by @sparky8251 on GitHub (Jan 6, 2019). This is part of #42 and #422. This one is a bit complicated. It has 2 tables and 3 indicies. The `Devices` table has 3 fields: `Id` which is `TEXT` and is the master key. `CustomName` which is `TEXT` `Capabilities` which is `TEXT` The `Tokens` table has 11 fields: `Id` which is `INTEGER` and is the master key. `AccessToken` which is `TEXT` `DeviceId` which is `TEXT` `AppName` which is `TEXT` `AppVersion` which is `TEXT` `DeviceName` which is `TEXT` `UserId` which is `TEXT` `UserName` which is `TEXT` `IsActive` which is `BIT` `DateCreated` which is `DATETIME` `DateLastActivity` which is `DATETIME` As for the indexes, looking at my DBs layout, its apparent that the tables should be joined into one rather than splitting them up and joining them. This will require code fixes to stop the joins and just directly query the DB. Would like confirmation on my take for this DB before proceeding. I have lacking experience with DBs.
OVERLORD added the backendstaleinvestigation labels 2026-02-06 19:26:42 +03:00
Author
Owner

@stale[bot] commented on GitHub (Jul 30, 2019):

Issues go stale after 60d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 7d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

@stale[bot] commented on GitHub (Jul 30, 2019): Issues go stale after 60d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 7d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on [Matrix or Social Media](https://jellyfin.readthedocs.io/en/latest/getting-help/).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#212