GreptimeTeam/greptimedb
Timestamp display precision should respect column schema
已關閉
#8,227 建立於 2026年6月3日
C-enhancementgood first issue
倉庫指標
- 星標
- (6,544 顆星)
- PR 合併指標
- (PR 指標待抓取)
描述
What type of enhancement is this?
User experience
What does the enhancement do?
Currently, when querying GreptimeDB through the MySQL CLI, timestamp rendering does not always respect the timestamp precision defined by the column schema. (Maybe pg cli also has this problem)
For example
create table
CREATE TABLE ts_precision_test (
ts_s TIMESTAMP(0),
ts_ms TIMESTAMP(3),
ts_us TIMESTAMP(6),
ts_ns TIMESTAMP(9),
v INT32,
TIME INDEX (ts_ms),
PRIMARY KEY (v)
);
insert data
INSERT INTO ts_precision_test VALUES (
'2026-06-02 03:50:00',
'2026-06-02 03:50:00.195',
'2026-06-02 03:50:00.195123',
'2026-06-02 03:50:00.195123456',
1
);
query data
SELECT * FROM ts_precision_test;
actual output
+---------------------+----------------------------+----------------------------+----------------------------+------+
| ts_s | ts_ms | ts_us | ts_ns | v |
+---------------------+----------------------------+----------------------------+----------------------------+------+
| 2026-06-02 03:50:00 | 2026-06-02 03:50:00.195000 | 2026-06-02 03:50:00.195123 | 2026-06-02 03:50:00.195123 | 1 |
+---------------------+----------------------------+----------------------------+----------------------------+------+
expected output
+---------------------+----------------------------+----------------------------+-------------------------------+------+
| ts_s | ts_ms | ts_us | ts_ns | v |
+---------------------+----------------------------+----------------------------+-------------------------------+------+
| 2026-06-02 03:50:00 | 2026-06-02 03:50:00.195 | 2026-06-02 03:50:00.195123 | 2026-06-02 03:50:00.195123456 | 1 |
+---------------------+----------------------------+----------------------------+-------------------------------+------+
Implementation challenges
No response