-
-
Notifications
You must be signed in to change notification settings - Fork 975
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
[Nozomi] Database feature doesn't work properly for Nozomi #1523
Comments
Might be caused by the archive format setting for Nozomi. Note: Filename settings are entirely irrelevant here. I think in your example, Maybe that's the problem, because if I recall it correctly, Nozomi is a site that breaks with typical booru conventions, so that one Could you try it with a config like this, for example? "nozomi": {
"search": {
"archive" : "./db/nozomi.sqlite3",
"filename": "{postid}-{num} {dataid}.{extension}",
"archive-format": "t_{search_tags}_{postid}_{dataid}"
}
}, |
Yes, this solves the problem. Maybe this setting should be the default for this site, since the current default is not exactly functional. |
… so they actually work for posts with more than 1 file. (fixes #1523)
Looks like Nozomi submissions are not uniquely represented in the database, making this feature largely useless for this extractor. The problem is reproducible on current stable version, 1.17.3
Config:
Sample output (assuming ./db/nozomi.sqlite3 is blank or absent):
Notice how only the 1st file in a sequence is processed properly.
The text was updated successfully, but these errors were encountered: