In the previous Time Fields - Integer Fields example, the time fields are written with second-level timestamps. But what if we want to control the granularity of time writing and write millisecond-level timestamps? We can use SoftTimeOption to control the granularity of the written time values.

Example SQL

Here's the MySQL table structure used in the following example code. Since we need to write values with a granularity finer than seconds, the field type uses big int for storage.

CREATE TABLE `user` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(45) NOT NULL,
  `status` tinyint DEFAULT 0,
  `created_at` bigint unsigned DEFAULT NULL,
  `updated_at` bigint unsigned DEFAULT NULL,
  `deleted_at` bigint unsigned DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

tip

If you try to test and view the SQL statements executed by ORM operations, it is recommended to enable debug mode (Documents: ORM Senior - Debug Mode), and the SQL statements will automatically be printed in the log output.

created_at Write Time

// INSERT INTO `user`(`name`,`created_at`,`updated_at`,`deleted_at`) VALUES('john',1731484186556,1731484186556,0)
g.Model("user").SoftTime(gdb.SoftTimeOption{
  SoftTimeType: gdb.SoftTimeTypeTimestampMilli,
}).Data(g.Map{"name": "john"}).Insert()

The SoftTimeType controls the time granularity, with the following granularity options:

const (
    SoftTimeTypeAuto           SoftTimeType = 0 // (Default) Auto detect the field type by table field type.
    SoftTimeTypeTime           SoftTimeType = 1 // Using datetime as the field value.
    SoftTimeTypeTimestamp      SoftTimeType = 2 // In unix seconds.
    SoftTimeTypeTimestampMilli SoftTimeType = 3 // In unix milliseconds.
    SoftTimeTypeTimestampMicro SoftTimeType = 4 // In unix microseconds.
    SoftTimeTypeTimestampNano  SoftTimeType = 5 // In unix nanoseconds.
)