| Summary: | Fractional seconds formatter value (zzz) not being read and applied to filename | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Matt Baker <kde.bugs> |
| Component: | AdvancedRename-file | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/5ff55ff03218bfc2d119e5251520cd68b40d220d | Version Fixed/Implemented In: | 8.5.0 |
| Sentry Crash Report: | |||
| Attachments: |
Import view preview file name
Rename view file name preview Test image |
||
|
Description
Matt Baker
2024-09-10 13:16:15 UTC
Created attachment 173527 [details]
Rename view file name preview
This is not a bug, only if a fractional second is present in the date in the DB, it can be adopted. The date usually comes from the original date in the metadata, but this rarely has a fractional second. Maik Thanks Maik. Okay, I can see your point of view for the renamer view but the import section seems like a bug: "Note however, when in Import view, the fractional seconds element is correctly displayed in the example output field when selecting an image, but when applying the format, the value also goes to 000." Please upload the image for testing. Maik Created attachment 173530 [details] Test image https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj Comment on attachment 173530 [details] Test image https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj Comment on attachment 173530 [details] Test image >https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj Comment on attachment 173530 [details] Test image <img src="https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj"> Comment on attachment 173530 [details] Test image <!DOCTYPE html> <html> <head> <title>Test image</title> </head> <body> <a href="https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj">https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj</a> </body> </html> Comment on attachment 173530 [details] Test image <!DOCTYPE html> <html> <head> <title>Test image</title> </head> <body> <a href="https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj">https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj</a> </body> </html> Oh no. What a mess. I didn't realise editing an attachment created a new comment each time... File is too large for upload. Link to file: https://1drv.ms/i/s!Ajr10IwsuvM9hNRmCdaMu-Iz1qxl4Q?e=oKLhNj Git commit 5ff55ff03218bfc2d119e5251520cd68b40d220d by Maik Qualmann. Committed on 10/09/2024 at 18:11. Pushed by mqualmann into branch 'master'. add support for fractional second when importing metadata M +1 -1 NEWS M +4 -0 core/utilities/import/main/importui.cpp https://invent.kde.org/graphics/digikam/-/commit/5ff55ff03218bfc2d119e5251520cd68b40d220d The general adoption of the fractional second into the database would not be a problem with SQLite. However, our MySQL database schema does not currently support time specifications with fractional seconds. This would require a major update for a MySQL database, so we will postpone this to a later digiKam version. Maik (In reply to Maik Qualmann from comment #14) > The general adoption of the fractional second into the database would not be > a problem with SQLite. However, our MySQL database schema does not currently > support time specifications with fractional seconds. This would require a > major update for a MySQL database, so we will postpone this to a later > digiKam version. > > Maik Thanks Maik. I'll give this a try when the weekly build is ready. Just tried the nightly build and it's now including the fractional data. Thanks! However, the value shown in the preview doesn't match what is actually being used as the file name for some reason. This is on the import view. The following image shows 2024-09-17 20-49-53.160.JPG as the filename preview with the renaming option set to [date:"yyyy-MM-dd hh-mm-ss.zzz"], but when I import the file, it names it to 2024-09-17 20-49-52.449.JPG Image: https://1drv.ms/i/s!Ajr10IwsuvM9hNUU-qDlR0n_8tpNXw?e=dbzJ93 The date view in the import tool can only be an approximate preview. It depends on the settings in the digiKam camera setup whether file metadata is read (makes the connection slower). Otherwise the date used comes from the file date. Maik |