# For DTable being built in Dagger.jl? Can I understand the rationale for having it vs just adding distributed arrays to DataFrames.jl?

**URL:** <https://discourse.julialang.org/t/for-dtable-being-built-in-dagger-jl-can-i-understand-the-rationale-for-having-it-vs-just-adding-distributed-arrays-to-dataframes-jl/65595>\
**Category:** General Usage\
**Created:** [July 31, 2021, 11:10am UTC](https://discourse.julialang.org/t/for-dtable-being-built-in-dagger-jl-can-i-understand-the-rationale-for-having-it-vs-just-adding-distributed-arrays-to-dataframes-jl/65595 "2021-07-31T11:10:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\
**Post date:** [July 31, 2021, 11:10am UTC](https://discourse.julialang.org/t/for-dtable-being-built-in-dagger-jl-can-i-understand-the-rationale-for-having-it-vs-just-adding-distributed-arrays-to-dataframes-jl/65595/1 "2021-07-31T11:10:13Z")

</div>

Would be interested in how the DTable in Dagger.jl works and the design behind it.

I imagine it’s something like, it’s harder to overload the methods in DataFrame than to have this work with Dagger’s DAG approach.