darktable-cli shall also use database for reading history stacks

[da-phil]

Is your feature request related to a problem? Please describe.

Currently darktable-cli only supports reading image processing histories from XMP sidecar files It's already possible to read styles from the data.db file (~/.config/darktable), so why shouldn't we also allow to read library.db to get the history stacks from? I'm not using sidecar files, hence generating ten thousands of XMP files just for always being able to use darktable-cli for exporting files is not so nice.

Describe the solution you'd like

I want to provide an additional commandline switch, which enables reading history stacks from the library.db file instead of sidecar files, for people who do not use sidecar files and rely soley on the central database of darktable.

[gth-42]

It'd be interesting to compare the time cost of I/O vs the database-only approach:

1. Add an ignore_xmp bool to common/image's _image_import_internal()
2. Add a new variant, say, dt_image_import_no_xmp.
3. Call it in cli with an --ignore-xmp flag.

I'm also in the likely-small 5-figure export group. Anything to improve throughput, but I suspect we're a tiny minority.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[da-phil]

The feature request is still relevant.