mirror of
https://github.com/databasus/databasus.git
synced 2026-04-06 00:32:03 +02:00
MariaDB Restore error message #87
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sylvainblanchouin on 3/4/2026
Databasus version
3.16.4
Operating system and architecture
Debian 12 x64
Describe the bug (please write manually, do not ask AI to summarize)
What happened:
I setup a fresh instance of Databasus in order to backup MariaDB 10.11.15. Backup is OK. When I want to test to restore, I have this error message :
mariadb failed: exit status 1 – stderr: ERROR 1064 (42000) at line 774994: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ''<p><img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAhcA...' at line 1
What I expected:
A successful restore without error message
Steps to reproduce
CREATE DATABASE IF NOT EXISTS
glpi/*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci */;USE
glpi;CREATE TABLE IF NOT EXISTS
glpi_itilfollowups(idint(10) unsigned NOT NULL AUTO_INCREMENT,itemtypevarchar(100) NOT NULL,items_idint(10) unsigned NOT NULL DEFAULT 0,datetimestamp NULL DEFAULT NULL,users_idint(10) unsigned NOT NULL DEFAULT 0,users_id_editorint(10) unsigned NOT NULL DEFAULT 0,contentlongtext DEFAULT NULL,is_privatetinyint(1) NOT NULL DEFAULT 0,requesttypes_idint(10) unsigned NOT NULL DEFAULT 0,date_modtimestamp NULL DEFAULT NULL,date_creationtimestamp NULL DEFAULT NULL,timeline_positiontinyint(1) NOT NULL DEFAULT 0,sourceitems_idint(10) unsigned NOT NULL DEFAULT 0,sourceof_items_idint(10) unsigned NOT NULL DEFAULT 0,PRIMARY KEY (
id),KEY
date(date),KEY
date_mod(date_mod),KEY
date_creation(date_creation),KEY
users_id(users_id),KEY
users_id_editor(users_id_editor),KEY
is_private(is_private),KEY
requesttypes_id(requesttypes_id),KEY
item(itemtype,items_id),KEY
sourceitems_id(sourceitems_id),KEY
sourceof_items_id(sourceof_items_id)) ENGINE=InnoDB AUTO_INCREMENT=79632 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
DELETE FROM
glpi_itilfollowups;INSERT INTO
glpi_itilfollowups(id,itemtype,items_id,date,users_id,users_id_editor,content,is_private,requesttypes_id,date_mod,date_creation,timeline_position,sourceitems_id,sourceof_items_id) VALUES(41950, 'Ticket', 69822, '2025-04-04 13:26:54', 2502, 0, '<p><img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAhcAAAJnCAYAAAAk+3GJAAAAAXNSR0IArs4c6QARiq33oV3c1EZFDv6QHTw5Jk/FjsbimkYyiMHOMPqxtsA2a9mi+7CvpxyVdK39OUx5tX3LwZ8N8MgwnWHN3W+aV5ZRg/C/4sPRs2LDxn4K/1G6EpLJ732H9s3wNqKwU4qjKkYfcUIFxeV2aU5SsKjoJK0qM7rxXWRLVyEpeaGRGolMyPQqV/8/Bvtcez2KDzschXlh9OzfByl5J/xjniQXbeANGQwGg+HLC+D/ARqrDAFEDW75AAAAAElFTkSuQmCC" data-upload_id="0.5224061834208611"></p>', 0, 1, '2025-04-04 13:26:54', '2025-04-04 13:26:54', 4, 0, 0);
Have you asked AI how to solve the issue?
Additional context / logs