# Hierarchical or multi-index for data frames

**URL:** <https://discourse.julialang.org/t/hierarchical-or-multi-index-for-data-frames/17076>\
**Category:** Data\
**Created:** [November 1, 2018, 11:41pm UTC](https://discourse.julialang.org/t/hierarchical-or-multi-index-for-data-frames/17076 "2018-11-01T23:41:35Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![MatthiasKauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/matthiaskauer/32/2192_2.png) [@MatthiasKauer](https://discourse.julialang.org/u/MatthiasKauer)\
**Post date:** [November 11, 2018, 8:33am UTC](https://discourse.julialang.org/t/hierarchical-or-multi-index-for-data-frames/17076/9 "2018-11-11T08:33:42Z")

</div>

Again, thank you so much for your input.

> Then there are currently two generic interfaces: Tables (which replaces DataStreams) and TableTraits. There’s hope that we could agree on a single common interface, but it’s still [under discussion](https://discourse.julialang.org/t/tables-jl-vs-tabletraits-jl-was-textparse-jl-is-fast-again/16982/1).

This thread really puts Tables.jl into context.

@piever: I really liked the two tutorials you linked. And nesting arrays into DataFrame seems really creative. Definitely has potential although probably not as standard operating procedure, like you said.

---

_[View the full topic](https://discourse.julialang.org/t/hierarchical-or-multi-index-for-data-frames/17076)._