2016-10-21, 08:10
Hi.
I think I've found a somewhat obscure bug.
In MyVideos DB I've found a circumstance where a row in table path doesn't get properly cleaned when a TV Show is removed from database.
The TV Information scraper for TheTVDB has a feature where you can specify "Use DVD Order" & "Use Absolute Ordering" instead of the default as returned from a standard scrape.
This writes an XML string to field strSettings in table path in DB MyVideos$.db
If this option is used, and the TV show in question is later deleted & removed from database but it has an entry in field strSettings then the row does not get deleted.
I'm not sure of the exact mechansim but this leads to subsequent library updates writing a WARNING: entry in kodi.log for the now deleted show on every rescan.
e.g. "WARNING: Process directory 'smb://USERNAME
ASSWORD@PATH//TVshowname/' does not exist - skipping scan."
Obviously it's not a showstopper, but more of a cosmetic/log-tidy-up bug than anything else.
I haven't raised a proper bug report in the TRAC system yet because I'm not certain it isn't an intended behaviour (i.e. retain scraper setting if show is later re-added to DB)
I tried searching to see if this was a known issue/behaviour but all the keywords led to far too many unrelated posts to be able to find anything specific.
If anyone knows better please and/or it's an already known issue or intended behaviour please post so I don't waste the devs time & this thread can be closed.
I've posted in `Support/General Support/OS-Independent` because I'd imagine the overall DB management is the territory of the core Kodi devs. If mods think it belongs more properly in `Support/Add-on Support/Metadata Scrapers` I'd be grateful if you could move this thread accordingly.
Cheers
--
kurai
I think I've found a somewhat obscure bug.
In MyVideos DB I've found a circumstance where a row in table path doesn't get properly cleaned when a TV Show is removed from database.
The TV Information scraper for TheTVDB has a feature where you can specify "Use DVD Order" & "Use Absolute Ordering" instead of the default as returned from a standard scrape.
This writes an XML string to field strSettings in table path in DB MyVideos$.db
If this option is used, and the TV show in question is later deleted & removed from database but it has an entry in field strSettings then the row does not get deleted.
I'm not sure of the exact mechansim but this leads to subsequent library updates writing a WARNING: entry in kodi.log for the now deleted show on every rescan.
e.g. "WARNING: Process directory 'smb://USERNAME
ASSWORD@PATH//TVshowname/' does not exist - skipping scan."Obviously it's not a showstopper, but more of a cosmetic/log-tidy-up bug than anything else.
I haven't raised a proper bug report in the TRAC system yet because I'm not certain it isn't an intended behaviour (i.e. retain scraper setting if show is later re-added to DB)
I tried searching to see if this was a known issue/behaviour but all the keywords led to far too many unrelated posts to be able to find anything specific.
If anyone knows better please and/or it's an already known issue or intended behaviour please post so I don't waste the devs time & this thread can be closed.
I've posted in `Support/General Support/OS-Independent` because I'd imagine the overall DB management is the territory of the core Kodi devs. If mods think it belongs more properly in `Support/Add-on Support/Metadata Scrapers` I'd be grateful if you could move this thread accordingly.
Cheers
--
kurai
