The comic_vine_volumes, comic_vine_volumes and comic_vine_publishertables
aren't related to each other, but are used by the ComicVine scraping code
to cache volume, issue and publisher query results, respectively. The
tables store the content (a JSON object) of the previous query in the
content column and doesn't break them down into individual records.
On Mon, Feb 24, 2020 at 8:37 PM Guy Incognito <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
There doesn’t seem to be any way to link these tables (via SQL).
I was expecting the COMIC_VINE_ISSUES table to include some way to like to
the COMIC_VINE_VOLUMES table.
Am I missing something? If not, is there a reason for the link not
existing?
I ask as I’m modifying a python script to pull basic information (CV
volume ID, issue ID and issue number) from ComicVine, which would be used
to look for missing issues in my library.
I guess I could modify the script to return volume and series names along
with the number...but IDs seemed better.
