# Common API for tabular data backends

**URL:** <https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546>\
**Category:** Data\
**Created:** [March 6, 2019, 7:49pm UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546 "2019-03-06T19:49:28Z")\
**Posts on this page:** 5\
**Page:** 3

<div class="post-metadata">

**Author:** ![tk3369](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tk3369/32/2824_2.png) [@tk3369](https://discourse.julialang.org/u/tk3369)\
**Post date:** [March 14, 2019, 7:02am UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546/42 "2019-03-14T07:02:43Z")

</div>

So Query.jl should be quite performant? Do you happen to have a benchmark suite that compares several query frameworks, similar to your csv file reader benchmark? That should be a fairly useful tool.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [March 14, 2019, 7:24am UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546/43 "2019-03-14T07:24:07Z")

</div>

> [@pdeffebach](#):
>
> `sf` tables just tibbles, but with geo-data attached to each observation, and they are wonderful to work with.

I don’t know the details, but isn’t this required since vectors in R are restricted to a few element types? In Julia, this is not the case, so most tabular implementations just work with generic elements out of the box.

---

<div class="post-metadata">

**Author:** ![pdeffebach](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pdeffebach/32/10320_2.png) [@pdeffebach](https://discourse.julialang.org/u/pdeffebach)\
**Post date:** [March 14, 2019, 11:58am UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546/44 "2019-03-14T11:58:09Z")

</div>

For sure, you could get basically the same functionality with a data frame with geo-data attached.

But there still might be good reasons for the own type, overloading plotting / mapping functions, or storing a geo-referencing system.

I just spent two weeks writing `sf` code and wanted to highlight that it basically represents the concept we are working towards.

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [August 27, 2020, 8:01pm UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546/45 "2020-08-27T20:01:47Z")

</div>

Joining the discussion a bit late to ask if there was an agreement about where this interface should be implemented? Is it TableOperations.jl? LightQuery.jl?

For example, now I need a simple table view that includes rows and columns in the query, but it doesn’t seem to exist. In TableOperations.jl, only column selectors exist.

---

<div class="post-metadata">

**Author:** ![non-Jedi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/non-jedi/32/3645_2.png) [@non-Jedi](https://discourse.julialang.org/u/non-Jedi)\
**Post date:** [August 28, 2020, 1:35am UTC](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546/46 "2020-08-28T01:35:43Z")

</div>

Isn’t that just the composition of the `select` and `filter` functions from TableOperations?

[Previous page](https://discourse.julialang.org/t/common-api-for-tabular-data-backends/21546.md?page=2)
