-
Notifications
You must be signed in to change notification settings - Fork 2.4k
default current_timestamp broken after update to 3.3.2 from 3.2.10 #50872
Copy link
Copy link
Closed
Labels
type/bugSomething isn't workingSomething isn't working
Description
Hello.
I made support for starrocks in goose library pressly/goose#810 and on version 3.2.10 it works fine.
But I update cluster to 3.3.2 and now there are empty values in datetime column, which created
tstamp datetime NULL default CURRENT_TIMESTAMP
Steps to reproduce the behavior (Required)
CREATE TABLE `migrations` ( `version_id` bigint(20) NOT NULL COMMENT "", `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT "", `is_applied` boolean NOT NULL COMMENT "", `tstamp` datetime NULL DEFAULT CURRENT_TIMESTAMP COMMENT "" ) ENGINE=OLAP PRIMARY KEY(`version_id`, `id`) DISTRIBUTED BY HASH(`id`) ORDER BY(`version_id`)insert into migrations (version_id, is_applied) values (0, true)select * from migrations
Expected behavior (Required)
0 1 1 2024-09-09 11:45:54
Real behavior (Required)
0 1 1 null
StarRocks version (Required)
3.3.2-857dd73
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
type/bugSomething isn't workingSomething isn't working