[Bug 308066] New: MySQL: How to delete data finally

[Sabine]

https://bugs.kde.org/show_bug.cgi?id=308066

            Bug ID: 308066
          Severity: wishlist
           Version: 2.6.0
          Priority: NOR
          Assignee: [hidden email]
           Summary: MySQL: How to delete data finally
    Classification: Unclassified
                OS: Linux
          Reporter: [hidden email]
          Hardware: Debian testing
            Status: UNCONFIRMED
         Component: Database
           Product: digikam

I deleted photos with incorrect date/time from digikam. The corresponding
entries in the database (MySQL) are not deleted, just the album is set to
"null". How can I get rid of the unwanted data (i.e. how can I
compress/reorganize the database)?

Furthermore the (in my case incorrect) data from the database is reused when I
try to reimport the photos again.

Is there a workaround (SQL-commands to "clean" the database)?

Reproducible: Always

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=308066

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Gilles Caulier <[hidden email]> ---
Install 2.9.0, run kdebugdialog, and turn on digiKam debug space.

Run digiKam froma console andreport all debug trace when you try to delete an
item.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Sabine]

https://bugs.kde.org/show_bug.cgi?id=308066

--- Comment #2 from [hidden email] ---
Created attachment 74422
  --> https://bugs.kde.org/attachment.cgi?id=74422&action=edit
the requested debug trace

With digikam 2.9.0 the deleted images are still in the MySQL-Database, just the
album is set to "null".

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=308066

--- Comment #3 from Marcel Wiesweg <[hidden email]> ---
The removed entries will definitely be deleted after a certain time (7-30
days).
Judging from 308065, you've already found the Read Metadata From Files to
Database functionality to fix your problem?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Sabine]

https://bugs.kde.org/show_bug.cgi?id=308066

--- Comment #4 from [hidden email] ---
> The removed entries will definitely be deleted after a certain time (7-30 days).
What does it depend from? Can I change that setting?

> Judging from 308065, you've already found the Read Metadata From Files to Database functionality to fix your problem?
Yes, my immediate problem is solved.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=308066

Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #5 from Marcel Wiesweg <[hidden email]> ---
It's a hardcoded heuristic. If you have more complete scans in short time, the
duration is less. The intention first and foremost not to lose data when files
are moved (which can mean first deleted, then reappearing), and for situations
were strange things happen and hard disks disappear. It gives a good fallback
for a lot of things which may go wrong.

Btw, the SQL to clean up is very simple:
"DELETE FROM Images WHERE status=3;"

Closing as wontfix as we dont want to change the feature.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=308066

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Mysql

--
You are receiving this mail because:
You are the assignee for the bug.