Description:
[Because there is no error report in log file (it occur when I operating the import wizard with no error) so I think suppling the log is unnecessary]
[But I can supply the example JSON file I used]
========= SQL Create Table
CREATE TABLE `finbook`.`test` (
`id` INT NOT NULL AUTO_INCREMENT,
`example_date` DATE NULL,
`other_data` VARCHAR(45) NULL,
PRIMARY KEY (`id`));
=========
========= Insert data SQL
INSERT INTO `finbook`.`test` (`example_date`, `other_data`) VALUES ('2025-06-09', 'abcd');
INSERT INTO `finbook`.`test` (`other_data`) VALUES ('abcd');
=========
========= JSON data file
[{"id": 1, "example_date": "2025-6-9", "other_data": "abcd"},
{"id": 2, "example_date": "", "other_data": "abcd"}]
=========
The data which "id: 1" is the normal data format, and the data which "id: 2" is the columns "example_date" with NULL contents. All above are the JSON file after I used "Data Export Wizard". But If I use "Data Import Wizard" with this JSON, the row data which "id: 2" will be ignored.
How to repeat:
I have a table with a column named delete_date, which is of type DATE and allows NULL values.
When I use the Data Export Wizard to export the table data as a JSON file, everything works fine.
However, the issue occurs when I attempt to import that same JSON file using the Data Import Wizard.
Even though the import process does not show any failure or error message, I noticed that rows with null values in the delete_date field are completely skipped during import.
In contrast, if I manually provide a valid DATE value in the same field, the row imports successfully.
This behavior seems incorrect, as the data exported by the tool should be fully compatible with the import process, including rows with null values in DATE fields.
I would appreciate it if the development team could investigate this issue. Thank you!
Suggested fix:
Since the column (delete_date) is defined as DATE and allows NULL values,
I believe the import process should be able to properly handle null entries instead of silently skipping them.
A potential fix could be adding a check during import to ensure that NULL values in JSON are accepted and preserved as-is,
or ensuring that null values are explicitly included in the exported JSON data (e.g. "delete_date": null) so that the importer can correctly interpret them.
Description: [Because there is no error report in log file (it occur when I operating the import wizard with no error) so I think suppling the log is unnecessary] [But I can supply the example JSON file I used] ========= SQL Create Table CREATE TABLE `finbook`.`test` ( `id` INT NOT NULL AUTO_INCREMENT, `example_date` DATE NULL, `other_data` VARCHAR(45) NULL, PRIMARY KEY (`id`)); ========= ========= Insert data SQL INSERT INTO `finbook`.`test` (`example_date`, `other_data`) VALUES ('2025-06-09', 'abcd'); INSERT INTO `finbook`.`test` (`other_data`) VALUES ('abcd'); ========= ========= JSON data file [{"id": 1, "example_date": "2025-6-9", "other_data": "abcd"}, {"id": 2, "example_date": "", "other_data": "abcd"}] ========= The data which "id: 1" is the normal data format, and the data which "id: 2" is the columns "example_date" with NULL contents. All above are the JSON file after I used "Data Export Wizard". But If I use "Data Import Wizard" with this JSON, the row data which "id: 2" will be ignored. How to repeat: I have a table with a column named delete_date, which is of type DATE and allows NULL values. When I use the Data Export Wizard to export the table data as a JSON file, everything works fine. However, the issue occurs when I attempt to import that same JSON file using the Data Import Wizard. Even though the import process does not show any failure or error message, I noticed that rows with null values in the delete_date field are completely skipped during import. In contrast, if I manually provide a valid DATE value in the same field, the row imports successfully. This behavior seems incorrect, as the data exported by the tool should be fully compatible with the import process, including rows with null values in DATE fields. I would appreciate it if the development team could investigate this issue. Thank you! Suggested fix: Since the column (delete_date) is defined as DATE and allows NULL values, I believe the import process should be able to properly handle null entries instead of silently skipping them. A potential fix could be adding a check during import to ensure that NULL values in JSON are accepted and preserved as-is, or ensuring that null values are explicitly included in the exported JSON data (e.g. "delete_date": null) so that the importer can correctly interpret them.