<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hey Andrey,</p>
<p>I just tried to reproduce the problem one hour ago with SQLite
and could not.</p>
<p>But I got a small MySQL database to work right now and was able
to reproduce</p>
<p>the corruption. I even got an error message in the trace:</p>
<p>"</p>
<p>digikam.dbengine: Prepare failed!<br>
digikam.dbengine: Failure executing query:<br>
"LOCK TABLE Tags WRITE;" <br>
Error messages: "QMYSQL3: Der Befehl konnte nicht initialisiert
werden" "This command is not supported in the prepared statement
protocol yet" 1295 2</p>
<p>"</p>
<p>So there definitely is a problem and as I see it, this will have
not worked for a longer time. Looks like an incomplete migration
from dbconfig to source code.<br>
</p>
<p>I will try to fix it.</p>
<p>Cheers,</p>
<p>Mario<br>
</p>
<br>
<div class="moz-cite-prefix">Am 09.08.2017 um 20:46 schrieb Andrey
Goreev:<br>
</div>
<blockquote type="cite"
cite="mid:CAOt0OUrzvxhzg0RbH8ommo7nS7rH6v3je1CShXuGyWXv=HVPLA@mail.gmail.com">
<div dir="ltr">
<div>
<div>Guys I believe I have experienced this bug too and I do
not use mysql (not anymore).<br>
</div>
I just got too busy and kind of gave up on the old pics and
moved on to the new pictures.<br>
<br>
</div>
So this might be a general database bug not just a mysql related
one.<br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>Best regards, <br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, Aug 9, 2017 at 12:17 PM, Gilles
Caulier <span dir="ltr"><<a
href="mailto:caulier.gilles@gmail.com" target="_blank"
moz-do-not-send="true">caulier.gilles@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Mario,<br>
<br>
You can ask to Swati. She improve the Mysql dtatabase
backend/schema<br>
while summer 2016, and i'm sure that she review this kind of
problem<br>
already. She has also certainly a Mysql DB reday to test.<br>
<br>
Gilles<br>
<br>
2017-08-09 20:07 GMT+02:00 Mario Frank <<a
href="mailto:mafrank@uni-potsdam.de"
moz-do-not-send="true">mafrank@uni-potsdam.de</a>>:<br>
> Hey Meku,<br>
><br>
> I think this is a bug. But I<br>
><br>
> 1) do not have a MySQL (and currently not the
possibility to create one) to<br>
> test and confirm<br>
><br>
> 2) Thus also cannot fix the problem shorthand.<br>
><br>
> I opened a bugzilla entry with your and mine findings
here:<br>
><br>
> <a href="https://bugs.kde.org/show_bug.cgi?id=383326"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://bugs.kde.org/show_bug.<wbr>cgi?id=383326</a><br>
><br>
> I hope one of the other devs can fix it faster than I.<br>
><br>
> Best,<br>
><br>
> Mario<br>
><br>
><br>
> "Am 09.08.2017 um 14:36 schrieb meku:<br>
> Studying the database there appears to be some
inconsistent data in the Tags<br>
> table causing this.<br>
><br>
> Tag B probably used to be a child of Tag A, but some
time ago Tag B was<br>
> moved to the root.<br>
><br>
> Tag B's 'pid' is '0' because it a child of the root
node, but the 'lft' and<br>
> 'rgt' fields have not been updated so still fall within
the range of Tag A's<br>
> 'lft' and 'rgt'.<br>
><br>
> If browsing using Tags with "Include Tag Sub-Tree"
enabled relies on the<br>
> 'lft' and 'rgt' fields then it would explain the
inconsistent behaviour I'm<br>
> seeing - and it appears it only happens to Tags that
have been moved in the<br>
> hierarchy.<br>
><br>
> Is this a bug, and is there a mysql query to repair
it?"<br>
><br>
> Am 08.08.2017 um 15:45 schrieb Mario Frank:<br>
><br>
> Hi Meku,<br>
><br>
> this is odd, as when the disabling solves the problem,
the unexpected items<br>
> must have<br>
><br>
> a tag that is a child tag of A. At least for sanity
reasons.<br>
><br>
> The source code itself looks good. Gilles, can you take
a look at the<br>
> definition of<br>
><br>
> getItemIDsInTagRecursive in the dbconfig? For me, it
looks correct, too.<br>
><br>
> Can you send a screenshot or something like this?<br>
><br>
> Cheers,<br>
> Mario<br>
><br>
> Am 08.08.2017 um 15:10 schrieb meku:<br>
><br>
> Hi Mario,<br>
><br>
> Yes, disabling "Include Tag Sub-Tree" hides the
unexpected items.<br>
><br>
> Tag B is not a child of Tag A and the unexpected items
do not have Tag A or<br>
> any of A's child tags.<br>
><br>
> I can work with mysql queries.<br>
><br>
> On 8 August 2017 at 22:55, Mario Frank <<a
href="mailto:mafrank@uni-potsdam.de"
moz-do-not-send="true">mafrank@uni-potsdam.de</a>>
wrote:<br>
>><br>
>> Hi Meku,<br>
>><br>
>> can you check the following?<br>
>><br>
>> In menu View: is the option "include tag tree" (I
do not know how it is<br>
>> called exactly in the English version, I have the
German one)<br>
>><br>
>> checked? If yes, images with subtags are also shown
in the browser and<br>
>> may have tag B.<br>
>><br>
>> Otherwise, do you have experience with MySQL
queries?<br>
>><br>
>> Cheers,<br>
>><br>
>> Mario<br>
>><br>
>><br>
>> Am 08.08.2017 um 14:46 schrieb meku:<br>
>> > I am seeing some inconsistent behaviour when
browsing items by Tags.<br>
>> ><br>
>> > Selecting a single tag (A) in the tree shows
all items with tag (A)<br>
>> > but also unrelated items with tag (B). So far
I have only discovered<br>
>> > this happening for a few specific tags, but it
continues happening<br>
>> > after restarting Digikam.<br>
>> ><br>
>> > If I use the Search for tag (A) then it shows
the expected results,<br>
>> > it's only within the Tag browser that this
issue is occurring.<br>
>> ><br>
>> > Using Digikam 5.7 appbundle with mysql.<br>
>><br>
><br>
><br>
><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>