Closed eugen-korentsov closed 7 months ago
This commit causes the bug.
mysql> SELECT COLUMN_NAME, COLUMN_DEFAULT, IS_NULLABLE, DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, NUMERIC_PRECISION, NUMERIC_SCALE, DATETIME_PRECISION, COLUMN_TYPE, EXTRA FROM information_schema.columns WHERE table_schema = 'test' and table_name = 'testy_test_force_update_request';
+---------------+-------------------+-------------+-----------+--------------------------+-------------------+---------------+--------------------+---------------------+-----------------------------------------------+
| COLUMN_NAME | COLUMN_DEFAULT | IS_NULLABLE | DATA_TYPE | CHARACTER_MAXIMUM_LENGTH | NUMERIC_PRECISION | NUMERIC_SCALE | DATETIME_PRECISION | COLUMN_TYPE | EXTRA |
+---------------+-------------------+-------------+-----------+--------------------------+-------------------+---------------+--------------------+---------------------+-----------------------------------------------+
| id | NULL | NO | int | NULL | 11 | 0 | NULL | int(11) unsigned | auto_increment |
| test_id | NULL | NO | int | NULL | 11 | 0 | NULL | int(11) unsigned | |
| testy_test_id | NULL | NO | int | NULL | 11 | 0 | NULL | int(11) unsigned | |
| is_affected | 0 | NO | tinyint | NULL | 3 | 0 | NULL | tinyint(3) unsigned | |
| created_at | CURRENT_TIMESTAMP | NO | timestamp | NULL | NULL | NULL | 0 | timestamp | |
| updated_at | CURRENT_TIMESTAMP | YES | datetime | NULL | NULL | NULL | 0 | datetime | DEFAULT_GENERATED on update CURRENT_TIMESTAMP |
+---------------+-------------------+-------------+-----------+--------------------------+-------------------+---------------+--------------------+---------------------+-----------------------------------------------+
6 rows in set (0.01 sec)
@Lloyd-Pottiger Maybe we should only exclude VIRTUAL GENERATED
column?
@eugen-korentsov @wd0517 Thank you~
b892f265e6c4cb02397e4b0fd14d834a035b093d fix this issue~
Schema:
updated_at field isn't created in bigquery, in csv 6 columns, it result to BigQuery error during import: