https://bugs.kde.org/show_bug.cgi?id=383326
Bug ID: 383326
Summary: Moving a tag does not update the parent tag correctly
Product: digikam
Version: 5.7.0
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: mario.fr...@uni-potsdam.de
Target Milestone: ---
>From Nabble:
http://digikam.1695700.n4.nabble.com/Browsing-by-tag-sometimes-shows-items-with-alternative-tag-td4703595.html
The user experienced a tag in tag view containing an image that has neither
this tag nor a child tag assigned. The image was only shown if images from the
subtags are configured to be shown, too.
After analysing the database values for the tags that were assigned to the
image, he found out, that the lft and rgt values were in the range of the tag
in which he was seeing the image. He assumes that he has moved the really
assigned tag some time ago.
After looking at the code, I assume there is a bug in the case of MySQL
databases.
In TagDragDropHandler::dropEvent, the call
CoreDbAccess().db()->moveTag(newParentTag) is emitted if a MySQL database is
configured. This is done in order to update the lft and rgt values as this is
not done by triggers, opposed to QSLite.
But in CoreDB::moveTag the parameter is never used, as it is commented out.
I can not test it as I do not have a MySQL database. Also, I am not sure how to
fix it without the possibility for testing.
I rated the severity as major as the database is corrupted.
--
You are receiving this mail because:
You are watching all bug changes.
