-
Have a working export command. As soon as I add the --dry-run option it causes the command to not work anymore and reports an error: Error Message and Crash Log
Loaded options from file /Volumes/WDSSD2TB/photo_library_export/osxphotos_backup.toml Crash Log contents: The above exception was the direct cause of the following exception: Traceback (most recent call last): Tried it two different ways: .toml config contents for above command
[export] report = "/Volumes/WDSSD2TB/photo_library_export/osxphotos_report_backup.sqlite" db = "/Volumes/WDSSD2TB/Macbook_Pro_14_PhotosLibrary_Full_Originals_Backup/Photos Library.photoslibrary" tmpdir = "/Volumes/WDSSD2TB/photo_library_export/osxphotos_tmp" directory = "{created.year}/{created.year}-{created.mm}" theme = "dark" sidecar = [ "xmp",] person_keyword = true keyword_template = [ Removed the verbose and dry-run from the command line and instead put it in the TOML file .toml config contents for above command
[export] update = true report = "/Volumes/WDSSD2TB/photo_library_export/osxphotos_report_backup.sqlite" db = "/Volumes/WDSSD2TB/Macbook_Pro_14_PhotosLibrary_Full_Originals_Backup/Photos Library.photoslibrary" tmpdir = "/Volumes/WDSSD2TB/photo_library_export/osxphotos_tmp" directory = "{created.year}/{created.year}-{created.mm}" theme = "dark" sidecar = [ "xmp",] person_keyword = true keyword_template = [ NOTE: If I leave verbose option ON and remove the dry run the commands work fine. If I remove the verbose option and leave only dry run (either way) it still gives same error. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Thanks for the detailed report. I see the problem, will work on a fix but probably will be next weekend before I can get to it. When used in --dry-run mode, osxphotos creates an in-memory copy of the backup database so as not to change the database (which is needed to calculate what to export). However, it currently does this by dumping the SQL for the database then loading that into a new database and it's exceeding the sqlite query length:
I'll open a new issue to fix this. The correct way is to use sqlite backup() |
Beta Was this translation helpful? Give feedback.
-
Fix implemented. Running test suite now. See #1071 |
Beta Was this translation helpful? Give feedback.
I think this is fixed in v0.60.1. Please upgrade and let me know if you still have the problem.