Open ArneAnka opened 2 years ago
There is "archive-format"
key which controls which fields are stored in the database record. I use it to combine several fields to make a record unique for some other extractor. It should work on "twitter"
.
Although stored as SQLite 3, gallery-dl does not use the archive file as a full-featured database. Archive database works like a checklist. I think gallery-dl use it solely for de-duplication; that is, when the metadata for a tweet is known, gallery-dl uses your "archive-format"
to generate a hash-like digest and compares that with records already in the database, it then skips downloading if the same record exists. It doesn't care what your "archive-format"
contains, but each record must be stable (doesn't change for the same source), and unique across all extractors. The record itself also has no structure; think of it as a single line in a text (txt) file. If you want structure (fields that map back to columns of a table or properties of a class), you need to design one yourself and make that transportable in a single line of text.
Hi!
Using version 1.23.0 of gallery-dl
Here is my configuration file:
Im investigating if
gallery-dl
can write more data to the database (in my case~/Pictures/gallery-dl/archive.sqlite3
), for example tweet content, images, post date of the tweet etc.I dont know how i otherwise would get that information. I somehow need to make an extra script to once again hit the url with, for example, python script. I would like to somehow display them locally.
And what about the logs? Every time i run gallery-dl, it seems to check EVERY already downloaded tweet.