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

--- Comment #4 from [email protected] ---
(In reply to Maik Qualmann from comment #1)
> I think you need to run "mariadb-upgrade" on your database(s). This must be
> done whenever a new server version is installed.
> 
> Maik

Thanks. However, running "mariadb-upgrade" or "check table ... for upgrade"
does not seem to have a permanent effect on this (mariadb 11.7.2, seemed to be
known for 10.11.8, see https://jira.mariadb.org/browse/MDEV-34210):

+-------------------------+-------+----------+------------------------------------------------------+
| Table                   | Op    | Msg_type | Msg_text                        
                    |
+-------------------------+-------+----------+------------------------------------------------------+
| digikamfaces.Identities | check | note     | Auto_increment checked and .frm
file version updated |
| digikamfaces.Identities | check | status   | OK                              
                    |
+-------------------------+-------+----------+------------------------------------------------------+
2 rows in set (0.000 sec)

MariaDB [digikamfaces]> check table Identities;
+-------------------------+-------+----------+---------------------------------------------------------------------------------------+
| Table                   | Op    | Msg_type | Msg_text                        
                                                     |
+-------------------------+-------+----------+---------------------------------------------------------------------------------------+
| digikamfaces.Identities | check | note     | Auto_increment will be checked
on each open until CHECK TABLE FOR UPGRADE is executed |
| digikamfaces.Identities | check | status   | OK                              
                                                     |
+-------------------------+-------+----------+---------------------------------------------------------------------------------------+
2 rows in set (0.001 sec)

Granted, this is not a Digikam bug.

But your no-exception fix should perhaps not only consider
digikamfaces.identities, but also digikamcore.DownloadHistory,
digikamcore.ImageCopyright, digikamcore.Searches,
digikamfaces.OpenCVLBPHRecognizer, digikamfaces.OpenCVLBPHistograms and
digikamthumbs.Thumbnails which behave similarly. 

Just in case this is relevant.

Heinz

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to