Bug 431035 - MariaDB error upgrading from stable to beta
Summary: MariaDB error upgrading from stable to beta
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (other bugs)
Version First Reported In: 7.2.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-01 16:15 UTC by Samuel
Modified: 2023-10-20 21:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 8.2.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel 2021-01-01 16:15:00 UTC
SUMMARY

I went from the last Digikam stable to the 7.2.0.2beta and received an error about the database. I uninstalled MariaDB and did a clean install of Digikam. Now i get this error:

 "You have insufficient privileges on the database.
Following privileges are not assigned to you:
 ALTER TABLE
Check your privileges on the database and restart digiKam."

How can I go about solving this or somehow just deleting everything any starting fresh?

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2021-01-01 16:22:59 UTC
We need more information, which operating system? Linux, MacOS, Windows? Do you use the internal or external MySQL server? Post the digiKam start log as described here:

https://www.digikam.org/contribute/

Maik
Comment 2 Samuel 2021-01-01 16:30:50 UTC
(In reply to Maik Qualmann from comment #1)
> We need more information, which operating system? Linux, MacOS, Windows? Do
> you use the internal or external MySQL server? Post the digiKam start log as
> described here:
> 
> https://www.digikam.org/contribute/
> 
> Maik

I have Windows 10, and I searched "Windows System Info" and nothing came up.

Also I deleted the database folder and it opened up a fresh copy of Digikam. The it asked to download some new face library. I restarted my digikam afterwards now it says "Failed to create tables in database."
Comment 3 Maik Qualmann 2021-01-01 16:41:22 UTC
What do you mean, you deleted the database folder? Why do you do that?
Which database type have you set in digiKam Setup under Database? SQLite, internal MySQL, or external MySQL?
With an external MySQL server, you have to set all rights correctly yourself and create the database. Otherwise we need the DebugView log.

Since you have already deleted everything and probably want to start over, you should also delete the digikamrc file in Appdata.

Maik
Comment 4 Samuel 2021-01-01 21:17:57 UTC
(In reply to Maik Qualmann from comment #3)
> What do you mean, you deleted the database folder? Why do you do that?
> Which database type have you set in digiKam Setup under Database? SQLite,
> internal MySQL, or external MySQL?
> With an external MySQL server, you have to set all rights correctly yourself
> and create the database. Otherwise we need the DebugView log.
> 
> Since you have already deleted everything and probably want to start over,
> you should also delete the digikamrc file in Appdata.
> 
> Maik

I deleted that and it started from scratch. Thank you!

The reason I had wanted to delete everything was because I have about 110 million photos and Digikam kept freezing/crashing whenever I tried opening so I just wanted to start fresh with one of my smaller albums instead of my entire catalog.
Comment 5 caulier.gilles 2021-01-01 21:55:05 UTC
110 millions of photo ? really ?

Gilles Caulier
Comment 6 caulier.gilles 2023-04-30 07:39:34 UTC
@Samuel

 digiKam 8.0.0 is out. This entry still valid with this release ?

Best regards

Gilles Caulier
Comment 7 caulier.gilles 2023-10-15 10:36:36 UTC
@Samuel,


This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:

https://files.kde.org/digikam/

This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110.

Thanks in advance

Gilles Caulier
Comment 8 Maik Qualmann 2023-10-20 21:08:15 UTC
Fixed with Bug 475874

Maik