`fwrite(dateTimeAs = "write.csv")` is not aligned with `write.csv()`
还没有人认领这个 Issue。
评估
调研方向
Start by reproducing the minimal example with fwrite(dateTimeAs = "write.csv"), write.csv(), and options("digits.secs"). Then locate the existing fwrite dateTimeAs coverage and determine how timestamp precision is selected; done means fwrite preserves the millisecond portion by default in the same way as write.csv, with regression coverage.
由索引模型根据 Issue 内容生成。
描述
I just tried to replace some write.csv calls with fwrite using its dateTimeAs = "write.csv" option and noticed that by default (without setting digits.secs) fwrite removes the millisecond portion from the timestamps, which is not (or no longer) the case when using write.csv.
The background was discussed here. However, it seems only a corresponding test was adapted and fwrite was not aligned with write.csv.
Is this intentional? I think it's confusing.
Minimal reproducible example
library(data.table)
options("digits.secs")
# options(digits.secs = 3L)
DT <- data.table(TS = as.POSIXct("2026-02-26 13:21:49.123"))
write.csv(DT, file = "write.csv", quote = FALSE, row.names = FALSE)
readLines("write.csv")
# [1] "TS" "2026-02-26 13:21:49.123"
fwrite(DT, file = "fwrite.csv", dateTimeAs = "write.csv")
readLines("fwrite.csv")
# [1] "TS" "2026-02-26 13:21:49"
sessionInfo()
R version 4.5.2 (2025-10-31 ucrt)
Platform: x86_64-w64-mingw32/x64
Running under: Windows 10 x64 (build 19045)
Matrix products: default
LAPACK version 3.12.1
locale:
[1] LC_COLLATE=English_United States.utf8 LC_CTYPE=English_United States.utf8
[3] LC_MONETARY=English_United States.utf8 LC_NUMERIC=C
[5] LC_TIME=English_United States.utf8
time zone: Europe/Berlin
tzcode source: internal
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] data.table_1.18.2.1
loaded via a namespace (and not attached):
[1] compiler_4.5.2 cli_3.6.5 tools_4.5.2 rstudioapi_0.18.0 pkgload_1.5.0
[6] rlang_1.1.7
- 主要语言
- R
- 星标
- 3.9k
- 派生
- 1.1k
- 平均合并
- 15 小时 51 分钟
- 30 天内合并 PR
- 3
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Rdatatable/data.table 的其他 Issue
-
as.data.table() recurses without end on a survival::Surv object (or any data.frame carrying one)未关闭
难度 2/5 1-3 小时 新手友好度 88/100
Rdatatable/data.table#7887 ·
-
test() doesn't distinguish plain NA_real_, NaN可能已有人在做 @MichaelChirico 于 69 天前认领。 未关闭consistency tests
难度 2/5 1-3 小时 新手友好度 68/100
Rdatatable/data.table#7853 · 3 条评论 ·
-
HAVE_LONG_DOUBLE is conditioned on but never set可能已有人在做 @venom1204 于 513 天前认领。 未关闭internals
难度 2/5 1-3 小时 新手友好度 65/100
Rdatatable/data.table#6938 · 1 条评论 ·
-
encoding fread
难度 2/5 1-3 小时 新手友好度 65/100
Rdatatable/data.table#5179 · 8 条评论 ·
-
documentation programming
难度 2/5 1-3 小时 新手友好度 68/100
Rdatatable/data.table#3199 · 3 条评论 ·
查看 Rdatatable/data.table 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
-
bug code cleaning
难度 2/5 1-3 小时 新手友好度 88/100
furrer-lab/abn#272 ·
-
难度 1/5 1 小时以内 新手友好度 92/100
philchalmers/SimDesign#106 ·
-
难度 1/5 1 小时以内 新手友好度 64/100
-
难度 1/5 1 小时以内 新手友好度 75/100
hturner/pkg-dev-ctv#57 ·