-
-
Notifications
You must be signed in to change notification settings - Fork 976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error encountered when using SQLite for the archive #553
Comments
What's the output of
I'm guessing your installed version of SQLite is older than 3.8.2 and therefore doesn't understand the |
You would be correct: Seems Centos7 requires 3.7. Time to install the latest. Hopefully everything will pick up the right version. :) python3 -c 'import sqlite3; print(sqlite3.sqlite_version)' |
Before you put in all the effort of installing a new version, you could just remove the clause from your local gallery-dl installation in Lines 743 to 744 in 1afb913
and I'll add a fallback into the next version. |
Thanks for the suggestion. Centos7 really depends on 3.7 and trying to upgrade to the latest produces a lot of packages going "You SURE you want to do this?". |
Thank you very much. Looks to be working now. Looking forward to your next release so I don't have to track this direct edit. It may be time to upgrade to Centos8 too. |
Oops, a wrong topic. Moved to: #1183 (comment) BTW
Yes, it increases the size by 70 %, however, with it the entries are ordered by the insert time. Using of a separate table for each |
I have gallery-dl 1.12.1 installed on Centos7 (Up to date) and I've set the following line in the gallery-dl.cof file in the extractor section:
"archive": "/home/archivist/bin/gallery-dl-cache.sqlite3",
When I run the following command:
gallery-dl -d rips/reddit/verylargeimages https://www.reddit.com/r/verylargeimages/new
I get the following error:
[reddit][warning] Failed to open download archive at '/home/archivist/bin/gallery-dl-cache.sqlite3' ('OperationalError: near "WITHOUT": syntax error')
The account the command is run on has full rights to the directory specified and a 0 byte file is written when the command starts.
Am I missing a step in either configuring or initializing the database?
The text was updated successfully, but these errors were encountered: