# Why JuliaDB.Table?

**URL:** <https://discourse.julialang.org/t/why-juliadb-table/11473>\
**Category:** Data\
**Created:** [June 6, 2018, 2:32pm UTC](https://discourse.julialang.org/t/why-juliadb-table/11473 "2018-06-06T14:32:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamii](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jamii/32/1373_2.png) [@jamii](https://discourse.julialang.org/u/jamii)\
**Post date:** [June 6, 2018, 2:32pm UTC](https://discourse.julialang.org/t/why-juliadb-table/11473/1 "2018-06-06T14:32:00Z")

</div>

IIRC the original JuliaDB release only had one datastructure, which was similar to the current JuliaDB.NDSparse. I’m curious why Table was added. Is this a UX thing, or so that they can dispatch differently, or some underlying implementation difference?

---

<div class="post-metadata">

**Author:** ![shashi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/shashi/32/1824_2.png) [@shashi](https://discourse.julialang.org/u/shashi)\
**Post date:** [June 6, 2018, 6:46pm UTC](https://discourse.julialang.org/t/why-juliadb-table/11473/2 "2018-06-06T18:46:38Z")

</div>

You’re right. It’s just extended API over the same implementation.