Error " request failed with status code 400 " raised when trying to import an Excel file

[okaeiz]

• Project Info

Node: v12.22.6
Arch: x64
Platform: linux
Docker: true
Database: mysql2
ProjectOnRootDB: true
RootDB: mysql2
PackageVersion: 0.84.12

• Steps To Reproduce
  When creating a new project using an Excel file, error " request failed with status code 400 " is raised. The column headers are visible but we cannot see the rest of the data ( rows haven't been imported ).
  We cannot also see the Kanban view and Calendar view of our databases.

• Expected behavior
  We expected to have our Excel file completely imported; with all rows and columns.

Join our discord : https://discord.gg/5RgZmkW for realtime help.

Node version : v12.22.1
Arch type: x64
Platform: linux
Docker: true
Database: sqlite3
packageVersion: 0.9.27

[wingkwong]

Able to reproduce only in docker-compose

[dstala]

We cannot also see the Kanban view and Calendar view of our databases.

Right now, Kanban & Calendar views are under development, not deployed yet. Grid/ Gallery & Form view are options available.

[wingkwong]

Checked with the user. The excel file contains data with Persian characters. By default, mysql is using latin1_swedish_ci. It can be proved by running the following SQL query.

SELECT SCHEMA_NAME 'database', default_character_set_name 'charset', DEFAULT_COLLATION_NAME 'collation' FROM information_schema.SCHEMATA;

You should see

+--------------------+---------+-------------------+
| database           | charset | collation         |
+--------------------+---------+-------------------+
| information_schema | utf8    | utf8_general_ci   |
| root_db            | latin1  | latin1_swedish_ci |
+--------------------+---------+-------------------+

Hence, adding the following line will change the character set and collation.

command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci

Example:

Running the same query

SELECT SCHEMA_NAME 'database', default_character_set_name 'charset', DEFAULT_COLLATION_NAME 'collation' FROM information_schema.SCHEMATA;

Result:

+--------------------+---------+--------------------+
| database           | charset | collation          |
+--------------------+---------+--------------------+
| information_schema | utf8    | utf8_general_ci    |
| root_db            | utf8mb4 | utf8mb4_unicode_ci |
+--------------------+---------+--------------------+

P.S - You may need to remove the existing volume mysql_db_data first.

[wingkwong]

Included an example in a9481dd.

[github-actions]

Fixed in v0.84.13.

[adamlaska]

Fixed in v0.84.13.