And you are correct, I am not willing to post my logs in a public forum. ![]() I simply do not have the time to chase a problem that’s simply an exercise in possibly identifying the problem without a solution. ![]() Order by metadata_items.title_sort collate icu_root asc, metadata_items.originally_available_at asc, metadata_items.id asc limit 100 Īs one potential test, if you run the above query, modified for your specific search query and library section id, against your database using Plex SQLite, does it come back with any results? If not, it’s definitely seems like something is wrong with the database/your search indexes that optimization isn’t fixing.Īs I said multiple times, I’m so appreciative of the effort. Metadata_items.library_section_id in (2) and Left join media_parts on media_dia_item_id=media_items.idįts4_metadata_titles_icu.title match 'Cidade* De* Deus*' and Left join media_items on media_tadata_item_id=metadata_items.id Join fts4_metadata_titles_icu on metadata_items.id=fts4_metadata_titles_icu.rowid You never said exactly when it started, so it could have began since the last scheduled maintenance.ĭo your server logs show any warnings/errors around the time you initiate the search (the line will contain GET /hubs/search?query=)?Īfter enabling EnableDatabaseTrace in preferences.xml (or the registry on Windows), I’m seeing the following query being run against my database, which returns the expected movie id based on its original title: select distinct metadata_items.id from metadata_items The basics are where you start when someone doesn’t explain what they’ve tried to resolve the problem so far.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |