Alternate Releases Table for Scenes #1688
metacarejeff
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Since Merging scenes is problematic, have a separate table for Alternate Releases
id, base_release_id, alternate_release_id -> Need a method to add scraped filenames to the base array or match on any releases filename array
You could one further this with a bigger change, would also handle re-releases nicely:
BaseScenes(current data minus studio/site specific data and dates)
SceneReleases(studio specifics/dates Filenames)
This is an imperfect SQL query that identifies multi-release scenes (add cast for a more accurate version)
SELECT scenes.scraper_id, ts.scraper_id, ts.scene_id,scenes.scene_id,ts.title from scenes join
(select * from scenes where scraper_id !='(Your Aggregate Site scraper here)' and title in
(SELECT title from scenes where scraper_id ='(Your Aggregate Sitel scraper here)')) ts on scenes.title = ts.title
order by title
Beta Was this translation helpful? Give feedback.
All reactions