https://bugs.kde.org/show_bug.cgi?id=451460
--- Comment #7 from Vincent Danjean <vdanjean...@free.fr> ---
By executing the following mysql commands:
```
update user set Super_priv='Y' where User='digikamuser';
FLUSH PRIVILEGES;
```
I've been able to go to the next mysql command. But this new one also fails
(with the same global behavior).
In the terminal, I can see this:
```
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikamdb"
DB Thumbs Name: "digikamthumbdb"
DB Face Name: "digikamfaces"
DB Similarity Name: ""
Connect Options: ""
Host Name: "localhost"
Host port: 3306
Internal Server: false
Internal Server Path: ""
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: "digikamuser"
Password: "XXXXXXXX"
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 10
digikam.coredb: Core database: makeUpdates 10 to 15
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Column count doesn't match
value count at row 1" "1136" 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV10ToV11" ]
Statement [ "REPLACE INTO temp_Tags SELECT * FROM Tags WHERE id != 0;" ]
digikam.coredb: Core database: schema update to V 11 failed!
digikam.coredb: Core database: cannot process schema initialization
digikam.general: KMemoryInfo: Platform identified : "LINUX"
digikam.general: KMemoryInfo: TotalRam: 33504178176
digikam.general: Allowing a cache size of 400 MB
QThreadStorage: Thread 0x7ffff7fc2b00 exited after QThreadStorage 12 destroyed
```
In mariadb logs, I can see this:
```
2022-03-13T19:07:51.776807Z 246 Connect digikamuser@localhost on
digikamdb using Socket
2022-03-13T19:07:51.776943Z 246 Init DB digikamdb
2022-03-13T19:07:51.777044Z 246 Query SET NAMES utf8mb3
2022-03-13T19:07:51.777179Z 246 Prepare SELECT ? + ?
2022-03-13T19:07:51.777237Z 246 Close stmt
2022-03-13T19:07:51.777261Z 246 Quit
2022-03-13T19:07:52.621166Z 247 Connect digikamuser@localhost on
digikamdb using Socket
2022-03-13T19:07:52.621331Z 247 Init DB digikamdb
2022-03-13T19:07:52.621415Z 247 Query SET NAMES utf8mb3
2022-03-13T19:07:52.621514Z 247 Prepare SELECT ? + ?
2022-03-13T19:07:52.621574Z 247 Close stmt
2022-03-13T19:07:52.621831Z 248 Connect digikamuser@localhost on
digikamdb using Socket
2022-03-13T19:07:52.621933Z 248 Init DB digikamdb
2022-03-13T19:07:52.622048Z 248 Query SET NAMES utf8mb3
2022-03-13T19:07:52.622176Z 248 Prepare SELECT ? + ?
2022-03-13T19:07:52.622191Z 248 Close stmt
2022-03-13T19:07:52.622342Z 248 Query DROP TABLE IF EXISTS PrivCheck
2022-03-13T19:07:53.639186Z 248 Query CREATE TABLE IF NOT EXISTS
PrivCheck
(id INT,
name VARCHAR(35))
ENGINE InnoDB
2022-03-13T19:07:57.806128Z 248 Query ALTER TABLE PrivCheck DROP
COLUMN name
2022-03-13T19:07:57.826204Z 248 Query DROP TABLE PrivCheck
2022-03-13T19:07:57.832284Z 248 Query DROP TABLE IF EXISTS PrivCheck
2022-03-13T19:07:57.833875Z 248 Quit
2022-03-13T19:07:57.833977Z 247 Query select table_name from
information_schema.tables where table_schema = 'digikamdb' and table_type =
'BASE TABLE'
2022-03-13T19:07:57.834987Z 247 Prepare SELECT value FROM Settings
WHERE keyword=?
2022-03-13T19:07:57.835067Z 247 Reset stmt
2022-03-13T19:07:57.835163Z 247 Execute SELECT value FROM Settings
WHERE keyword='DBVersion'
2022-03-13T19:07:57.835381Z 247 Close stmt
2022-03-13T19:07:57.835431Z 247 Prepare SELECT value FROM Settings
WHERE keyword=?
2022-03-13T19:07:57.835444Z 247 Reset stmt
2022-03-13T19:07:57.835482Z 247 Execute SELECT value FROM Settings
WHERE keyword='DBVersionRequired'
2022-03-13T19:07:57.835585Z 247 Close stmt
2022-03-13T19:07:57.835677Z 247 Query BEGIN WORK
2022-03-13T19:07:57.835819Z 247 Query DROP TRIGGER IF EXISTS
temp_insert_tagstree
2022-03-13T19:07:57.837309Z 247 Query DROP TRIGGER IF EXISTS
insert_tagstree
2022-03-13T19:07:57.838890Z 247 Query DROP TRIGGER IF EXISTS
delete_tagstree
2022-03-13T19:07:57.840331Z 247 Query DROP TRIGGER IF EXISTS
move_tagstree
2022-03-13T19:07:57.843124Z 247 Query DROP TABLE IF EXISTS temp_Tags
2022-03-13T19:07:57.851436Z 247 Query DROP TABLE IF EXISTS TagsTree
2022-03-13T19:07:57.858627Z 247 Query DROP VIEW IF EXISTS TagsTree
2022-03-13T19:07:57.860223Z 247 Query CREATE TABLE IF NOT EXISTS
temp_Tags
(id INTEGER,
pid INTEGER,
name LONGTEXT CHARACTER SET utf8 COLLATE utf8_general_ci,
icon BIGINT,
iconkde LONGTEXT CHARACTER SET utf8 COLLATE
utf8_general_ci,
lft INTEGER,
rgt INTEGER)
ENGINE InnoDB
2022-03-13T19:07:57.873927Z 247 Query CREATE TABLE IF NOT EXISTS
TagsTree
(id INTEGER NOT NULL,
pid INTEGER NOT NULL,
UNIQUE (id, pid))
ENGINE InnoDB
2022-03-13T19:07:57.887722Z 247 Query CREATE TRIGGER
temp_insert_tagstree AFTER INSERT ON temp_Tags
FOR EACH ROW INSERT INTO TagsTree SELECT NEW.id, NEW.pid
UNION SELECT NEW.id, pid FROM TagsTree WHERE id = NEW.pid
2022-03-13T19:07:57.891701Z 247 Query REPLACE INTO temp_Tags SELECT *
FROM Tags WHERE id != 0
2022-03-13T19:07:57.893000Z 247 Query ROLLBACK
2022-03-13T19:07:57.893129Z 247 Prepare REPLACE INTO Settings VALUES
(?,?)
2022-03-13T19:07:57.893173Z 247 Reset stmt
2022-03-13T19:07:57.893210Z 247 Execute REPLACE INTO Settings VALUES
('DBVersion','10')
2022-03-13T19:07:57.894267Z 247 Close stmt
2022-03-13T19:07:57.894334Z 247 Prepare REPLACE INTO Settings VALUES
(?,?)
2022-03-13T19:07:57.894350Z 247 Reset stmt
2022-03-13T19:07:57.894407Z 247 Execute REPLACE INTO Settings VALUES
('DBVersionRequired','5')
2022-03-13T19:07:57.895533Z 247 Close stmt
```
Regards,
Vincent
--
You are receiving this mail because:
You are watching all bug changes.
