Search the Community

Hey there, I've recently had to perform a restore from backup of Emby on my Qnap TS-451+, For the most part everything is restored and is currently functioning to my satisfaction. Having said that, my current issue is a cosmetic effect rather than some issue that concerns Emby's functioning or operation. I'm trying to restore the 'Recently Added' view. In restoring from backup, I first did a complete uninstall of the previous instance of Emby Server. I then re-installed Emby Server and restored from backup. The detailed process that I followed came from Emby Wiki. As you might expect, the order of movies displayed in the Recently Added view has been randomized. My desire is to have the order of this view restored to what it was when the backup was originally taken. What I've been able to gather is that the library.db file is the database for the Emby library. There are many tables in this database but I think the table that has the info I wish to restore/change is the MediaItems table. There are 4 date fields in that table. DateCreated, DateModified, DateLastSaved & DateLastRefreshed. Using a single movie, I queried those fields from the backed up version of the library.db database. I constructed a SQL query that would update the timestamps for this movie in a copy of the Live library.db file. The query finished without issue, but I didn't get the desired result. So, my question is, do I have the correct database and fields? Are there any additional tables/fields that I need to be changing/updating in addition to these fields? What other precautions should I be considering? TIA

Greetings! I have been living with a "ghost" playlist issue for some time now (placed a m3u file in a lib folder, then deleted it, then added it back, and since the playlist contents have been "frozen"), so today decided to give a manual fix a try inspecting/manipulating the db directly. I think the root cause is that the record in the db does not have a path to the corresponding m3u file anymore Because of this I decided (after a db backup) to attempt both UPDATE and DELETE of the record, but in both cases I get back the error in the title... My experience with sqlite is non-existent, so I tried doing this from multiple clients (extenal dBeaver adapter, TNAS's pre-installed 'sqlite3' binary, and again using the TNAS's python + sqlite adapter), but the error is consistent. Does anybody have any suggestion / had similar issues? Thanks in advance ---- Device: F2-220 TOS version: 4.0.13 Emby Server version: 4.1.0.1