Your Question

In Product environment, filed set default null is not allowed. Thus we usually set create/update time field default value as "1970-01-01 00:00:00". As a result, when create or update a record, "created_at,updated_at" filed did not work as I expected(Timestamp Tracking).

The document you expected this should be explained

Expected answer

I want official support feature of Timestamp Tracking even if "created_at,updated_at" set "1970-01-01 00:00:00"(unix timestamp 0sec)

Comment From: wuzhiguocarter

table example, in UTC+8 time zone

CREATE TABLE `op_log` (
    `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT '主键id',
    `op_code` int(11) NOT NULL DEFAULT 0 COMMENT '操作码: 1:新增 2:修改 3:删除',
    `table_name` varchar(255) NOT NULL DEFAULT '' COMMENT '操作的表',
    `record_id` bigint(20) unsigned NOT NULL DEFAULT 0 COMMENT '操作的表记录的主键id',
    `msg` text COMMENT '修改操作详情, json序列化修改前后的记录; 非修改场景可置空',
    `operator` varchar(128) NOT NULL DEFAULT '' COMMENT '最后操作人或system',
    `created_at` timestamp NOT NULL DEFAULT '1970-01-01 08:00:00' COMMENT '操作时间',
    PRIMARY KEY (`id`)
) ENGINE = InnoDB AUTO_INCREMENT = 1 DEFAULT CHARSET = utf8 COMMENT = '操作日志表';

Comment From: a631807682

https://gorm.io/docs/data_types.html#Scanner-x2F-Valuer