rbind with lubridate Period broken

Open
#1,454 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
data

Research direction

Start by reproducing the issue with rbind and lubridate Period columns using the three examples in the report, then compare the data.table and data.frame results. Trace the rbind entry point to determine why the second Period value becomes 20H 0M 0S; done means preserving the values or clearly warning about the limitation.

Written by the indexing model from the issue text.

Description

[rbind|cbind|merge]list non-atomic column

Hi,

rbind-ing two data.tables (or a data.table and a data.frame) with a lubridate Period column is broken:

x<-data.table(dauer = hm("20:00"))
y<-data.table(dauer = hm("32:00"))

rbind(x,y)
rbind(as.data.frame(x), y)
rbind(as.data.frame(x), as.data.frame(y))

yields

> x<-data.table(dauer = hm("20:00"))
> y<-data.table(dauer = hm("32:00"))
> 
> rbind(x,y)
       dauer
1: 20H 0M 0S
2: 20H 0M 0S
> rbind(as.data.frame(x), y)
       dauer
1: 20H 0M 0S
2: 20H 0M 0S
> rbind(as.data.frame(x), as.data.frame(y))
      dauer
1 20H 0M 0S
2 32H 0M 0S

I'm not sure whether that's a known limitation but Google doesn't find anything and if it is it should print a warning. :)

Ciao
Stefan

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.