import of DB doesn't work

[D-nov]

Describe the bug
Install mysql, install antares, create new empty DB , import previously dumped DB. It now shows a modal that is doing something, however upon completion there is no trace of any imported data.

To Reproduce
See description above. If not clear I can add video.

Expected behavior
DB import works and i can see the imported tables and data.

Screenshots
Don't have atm, but can attach later.

Application (please complete the following information):

• App client [e.g. MariaDB]
• Installation source: [e.g. exe]

Environment (please complete the following information):

• OS name: [e.g. Windows 10]
• DB name [e.g. MariaDB]

Additional context
Add any other context about the problem here.

[Fabio286]

Hi Danny,
Could you provide me a sql with a dump for which you get the problem?

[D-nov]

No, unfortunately, this was too long ago during some tutorial.
Since then i use the command line to import DBs.

If I ever use the UI again and this happens i'll open new issue.
For now I assume it was solved because recently i saw a friend import DB from the UI successfully.

[D-nov]

Ok, I found an SQL that causes it to not import anything, however I cannot share it.
Here are the errors I see during the import:

Also after letting it continue (hopefully until the end), I noticed at some point Antares became completely black (this is on M1 MacBook, it didn't happen on ubuntu on a toaster laptop) - no UI at all, just black background.

Unfortunately the SQL dump is huge and I could not even open it, however I managed to extract a small snippet with one table. Hopefully it's helpful.

-- Server version	10.3.39-MariaDB

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `panda`
--

DROP TABLE IF EXISTS `panda`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `panda` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(255) NOT NULL COMMENT 'name name',
  `action` varchar(255) NOT NULL COMMENT 'action  name',
  `created_at` timestamp NULL DEFAULT NULL,
  `updated_at` timestamp NULL DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `panda`
--

From here on it inserts data and continues with next tables...

[Fabio286]

Thank you for the SQL!

The error that comes up is the same as #646 even though you are not using the utf8mb3 charset. It has been a while since this problem and I will try to see if there is any solution.

As for the problem you are experiencing on macOS, I will try to figure out the possible causes, but I have no way to test because I don't have computers with that operating system.