[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #28 from Maik Qualmann --- Yes, the FOREIGN_KEY_CHECKS patch is included into git/master. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #27 from swatilodh...@gmail.com --- Maik, Could your last patch be included before 5.0.0 ? -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #26 from Maik Qualmann --- I think that this solution is better at the moment. I have set this problem on my todo list, to find a clean solution for the DB. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In|

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Maik Qualmann changed: What|Removed |Added Attachment #99765|0 |1 is obsolete|

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #24 from Maik Qualmann --- No, the entry does not exist here in the DB. Strange. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #23 from swatilodh...@gmail.com --- (In reply to Maik Qualmann from comment #22) > Created attachment 99765 [details] > removeStaleAlbum.patch > > This patch removes stale album function. Swati, you can test it please. The deleted album is

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #22 from Maik Qualmann --- Created attachment 99765 --> https://bugs.kde.org/attachment.cgi?id=99765&action=edit removeStaleAlbum.patch This patch removes stale album function. Swati, you can test it please. Maik -- You are receiving t

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Maik Qualmann changed: What|Removed |Added Attachment #99742|0 |1 is obsolete|

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #21 from Maik Qualmann --- I wonder just what need the stale album function. Perhaps Marcel can give an indication. I have in the CollectionScanner this function replaced with CoreDB::deleteAlbum(). It seems to work without problems. I creat

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #20 from Richard Mortimer --- I like the look of Maik's patch. It does seem to be working in a portable way that does not rely on any magic database primary key values. A deleted AlbumRoot is easy to identify too. A few comments on the patc

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #19 from swatilodh...@gmail.com --- (In reply to Maik Qualmann from comment #18) > Created attachment 99742 [details] > albumRoot.patch > > A first new patch, it works. The question is, is correct and can solved this > problem? Well, it did

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #18 from Maik Qualmann --- Created attachment 99742 --> https://bugs.kde.org/attachment.cgi?id=99742&action=edit albumRoot.patch A first new patch, it works. The question is, is correct and can solved this problem? Maik -- You are rece

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Maik Qualmann changed: What|Removed |Added Attachment #99669|0 |1 is obsolete|

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #17 from swatilodh...@gmail.com --- Richard, Could you please provide your suggestions here? Thank you. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #16 from Johannes Hirte --- (In reply to swatilodha27 from comment #15) > Is it possible to already have a "Fake Album" row when the DB is initially > created? > In the DB schema file, adding a query: > // > INSERT INTO AlbumRoots values(0,

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #15 from swatilodh...@gmail.com --- Is it possible to already have a "Fake Album" row when the DB is initially created? In the DB schema file, adding a query: // INSERT INTO AlbumRoots values(0, "Fake Album Root", 0, 0, NULL, NULL); // This

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Richard Mortimer changed: What|Removed |Added CC||richm+...@oldelvet.org.uk --- Comment #14 fr

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #13 from Johannes Hirte --- Patch works for me with MySQL/MariaDB. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Maik Qualmann changed: What|Removed |Added Summary|Album visible even after|Album visible even after |del