Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
This works as designed for the time being. If you create a timestamp with DEFAULT CURRENT_TIMESTAMP in the visual editor it scripts and displays correctly.
We are aware of the ON UPDATE CURRENT_TIMESTAMP issue on MySQL. The Create Table syntax of Mysql 5.0+, for column type time_stamp, if not null, which is default if not set, the table will create this column with a default value of CURRENT_TIMESTAMP and a trigger ON UPDATE SET COLUMN CURRENT_TIMESTAMP....
@ivan: lets discuss whether we need to make any changes or not to support schema sync.
@ivan: lets discuss whether we need to make any changes or not to support schema sync.
The extraction and scripting for this is working correctly. The table GUI doesn't have support for ON UPDATE CURRENT_TIMESTAMP property. This will require gui changes and there are varying differences with how this is supported in the latest versions. I recommend pushing issue to future as enhancement.
The extraction and scripting for this is working correctly. The table GUI doesn't have support for ON UPDATE CURRENT_TIMESTAMP property. This will require gui changes and there are varying differences with how this is supported in the latest versions. I recommend pushing issue to future as enhancement.
Issue #10933 |
| New |
Completion |
| No due date |
| No fixed build |
| No time estimate |
This works as designed for the time being. If you create a timestamp with DEFAULT CURRENT_TIMESTAMP in the visual editor it scripts and displays correctly.
We are aware of the ON UPDATE CURRENT_TIMESTAMP issue on MySQL. The Create Table syntax of Mysql 5.0+, for column type time_stamp, if not null, which is default if not set, the table will create this column with a default value of CURRENT_TIMESTAMP and a trigger ON UPDATE SET COLUMN CURRENT_TIMESTAMP....