DataFrames.jl
DataFrames.jl copied to clipboard
In-memory tabular data in Julia
If both tables in join-operations are fitting into `Int32` range (probably a common case) then we can use `Int32` instead of `Int` for indexing. This should speed up things.
[On Slack](https://julialang.slack.com/archives/CQQ32Q9C5/p1599642920077900), I wrote that I like the new `tidyr::pivot_` functions (https://tidyr.tidyverse.org/articles/pivot.html) because the names make it really obvious what they do, and they have good arguments for indicating what...
It would be a useful feature if `stack` and `melt` could be implemented over multiple sets of variables. For example from this: ``` 2×5 DataFrame │ Row │ ID │...
Congratulations on release 1.0.0 Regarding the missing values in the describe() function would it be possible to drop the skipmissing() function? The reason for this is purely performance wise. To...
This came up yesterday on slack We have `@chain` and `@pipe` etc. which make it easier to modify data without creating tons of intermediate names. We also have `transform!`, `select!`,...
I'm not sure if it is by design, but I was slightly surprised by the way `UInt` are displayed when in a `DataFrame` compared to regular vectors, _i.e._ decimal vs....
Currently `combine(gd, :x => maximum)` returns a `PooledArray` if the input is a `PooledArray`, but `combine(gd, :x => (x -> maximum(x)))` returns an `Array`. We should make this consistent. (`combine(gd,...
This has been discussed in several places I create a separate issue for this to keep track of it as it is an important functionality I think. What we want...
It seems that dealing with missing values is one of the most painful issues we have, which goes against the very powerful and convenient DataFrames API. Having to write things...
@ronisbr - I open this issue to keep track of to-do related to PrettyTables.jl: 1. coverage of show.jl is quite poor now: https://codecov.io/gh/JuliaData/DataFrames.jl/tree/master/src/abstractdataframe; it would be great to add more...