Why Navicat premium does not support Mysql8,
Why there is no default CURRENT_TIMESTAMP options timestamp type

CodePudding user response:

Navicat premium support mysql8, need to modify the configuration, 8 start mysql password policy has modified

In addition, current_timestamp also support this option, I test no problem

 
mysql> Select the version (); 
+ -- -- -- -- -- -- -- -- -- -- - + 
(1) | | version 
+ -- -- -- -- -- -- -- -- -- -- - + 
| 8.0.19 | 
+ -- -- -- -- -- -- -- -- -- -- - + 
1 row in the set (0.00 SEC) 

mysql> The create table t4 (id int, last_update TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP); 
Query OK, 0 rows affected (0.03 SEC) 

mysql> Insert into t4 (id) values (1); 
Query OK, 1 row affected (0.01 SEC) 

mysql> Select * from t4; 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
| | id last_update | 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
| 1 | 2020-09-11 09:28:41 | 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
1 row in the set (0.00 SEC) 

mysql> The update t4 set id=2 where id=1; 
Query OK, 1 row affected (0.01 SEC) 
The Changed Rows matched: 1:1 Warnings: 0 

mysql> Select * from t4; 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
| | id last_update | 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
| | 2020-09-11 09:28:57 | 
+ + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + 
1 row in the set (0.00 SEC) 

CodePudding user response:

Does is to modify the password format to use Mysql8, and current_timestamp in Navicat premium there is really no, or write their own, or export after oneself add then channelled back to
But long before these problems, especially current_timestamp this problem I see posts online from 2017 have this problem, don't know why the official repair,