Server Version#: 1.40.0.7998
Player Version#: N/A
Saw this error during the database migrations:
Feb 14, 2024 15:40:06.674 [140475172698936] ERROR - SQLITE3:0x80000001, 1, no such column: metadata_items.slug in "select metadata_items.id as 'metadata_items_id', metadata_items.library_section_id as 'metadata_items_library_section_id', metadata_items.parent_id as 'metadata_items_parent_id', metadata_items.metadata_type as 'metadata_items_metadata_type', metadata_items.guid as 'metadata_items_guid', metadata_items.slug as 'metadata_items_slug', metadata_items.hash as 'metadata_items_hash', metadata_items.media_item_count as 'metadata_items_media_item_count', metadata_items.title as 'metadata_items_title', metadata_items.title_sort as 'metadata_items_title_sort', metadata_items.original_title as 'metadata_items_original_title', metadata_items.studio as 'metadata_items_studio', metadata_items.rating as 'metadata_items_rating', meta
Feb 14, 2024 15:40:06.675 [140475172698936] ERROR - Thread: Uncaught exception running async task which was spawned by thread 140475185257272: sqlite3_statement_backend::prepare: no such column: metadata_items.slug for SQL: select metadata_items.id as 'metadata_items_id', metadata_items.library_section_id as 'metadata_items_library_section_id', metadata_items.parent_id as 'metadata_items_parent_id', metadata_items.metadata_type as 'metadata_items_metadata_type', metadata_items.guid as 'metadata_items_guid', metadata_items.slug as 'metadata_items_slug', metadata_items.hash as 'metadata_items_hash', metadata_items.media_item_count as 'metadata_items_media_item_count', metadata_items.title as 'metadata_items_title', metadata_items.title_sort as 'metadata_items_title_sort', metadata_items.original_title as 'metadata_items_original_title', metadata_items.studio as 'metadata_items_studio', metadata_items.rating as 'metadata_items_rating', metadata_items.audience_rating as 'metadata_items_audience_rating', metadata_items.rating_count as 'metadata_items_rating_count', metadata_items.tagline as 'metadata_items_tagline', metadata_items.edition_title as 'metadata_items_edition_title', metadata_items.summary as 'metadata_items_summary', metadata_items.content_rating as 'metadata_items_content_rating', metadata_items.content_rating_age as 'metadata_items_content_rating_age', metadata_items.'index' as 'metadata_items_index', metadata_items.absolute_index as 'metadata_items_absolute_index', metadata_items.duration as 'metadata_items_duration', metadata_items.user_thumb_url as 'metadata_items_user_thumb_url', metadata_items.user_art_url as 'metadata_items_user_art_url', metadata_items.user_banner_url as 'metadata_items_user_banner_url', metadata_items.user_music_url as 'metadata_items_user_music_url', metadata_items.user_fields as 'metadata_items_user_fields', metadata_items.originally_available_at as 'metadata_items_originally_available_at', metadata_items.available_at as 'metadata_items_available_at', metadata_items.expires_at as 'metadata_items_expires_at', metadata_items.refreshed_at as 'metadata_items_refreshed_at', metadata_items.year as 'metadata_items_year', metadata_items.added_at as 'metadata_items_added_at', metadata_items.created_at as 'metadata_items_created_at', metadata_items.updated_at as 'metadata_items_updated_at', metadata_items.changed_at as 'metadata_items_changed_at', metadata_items.resources_changed_at as 'metadata_items_resources_changed_at', metadata_items.tags_genre as 'metadata_items_tags_genre', metadata_items.tags_collection as 'metadata_items_tags_collection', metadata_items.tags_director as 'metadata_items_tags_director', metadata_items.tags_writer as 'metadata_items_tags_writer', metadata_items.tags_star as 'metadata_items_tags_star', metadata_items.deleted_at as 'metadata_items_deleted_at', metadata_items.tags_country as 'metadata_items_tags_country', metadata_items.extra_data as 'metadata_items_extra_data' from metadata_items where guid=?
The error seems to have happened while the migration 202309200913 was running.
It doesn’t seem to have affected anything and the migrations continued running after this log so I am not sure whether it’s something to be concerned about or not.
