# JuliaDB, dataframes: Speculations over the future of data packages

**URL:** <https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012>\
**Category:** Data\
**Created:** [August 24, 2018, 7:58pm UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012 "2018-08-24T19:58:56Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [November 5, 2019, 10:37pm UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012/21 "2019-11-05T22:37:23Z")

</div>

The curly brackets you don’t have to use in the Query.jl case. They simplify a couple of scenarios _a lot_, but if you want you can also just use plain old vanilla syntax for named tuples instead.

The use of macros in Query.jl is pretty simple: to the user they really just look like functions. So, yes, a couple more `@` appear in the code, but I don’t think they actually show up in syntactically difficult positions (or at least I hope so).

---

<div class="post-metadata">

**Author:** ![derekmahar](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/derekmahar/32/216439_2.png) [@derekmahar](https://discourse.julialang.org/u/derekmahar)\
**Post date:** [August 20, 2020, 2:44pm UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012/22 "2020-08-20T14:44:02Z")

</div>

> [@pdeffebach](#):
>
> Check out `@linq` 's new features.

Where may I find `@linq`?

---

<div class="post-metadata">

**Author:** ![bramtayl](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bramtayl/32/3614_2.png) [@bramtayl](https://discourse.julialang.org/u/bramtayl)\
**Post date:** [August 20, 2020, 2:54pm UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012/24 "2020-08-20T14:54:00Z")

</div>

I’m pretty happy with LightQuery right now; an alternative to consider.

---

<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:** [August 20, 2020, 6:35pm UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012/25 "2020-08-20T18:35:26Z")

</div>

`@linq` lives in DataFramesMeta. But DataFrames now has `transform` in Base that is very robust. Combined with `Pipe.jl` I think it’s almost a drop-in replacement.

---

<div class="post-metadata">

**Author:** ![gaspardelanuit](https://avatars.discourse-cdn.com/v4/letter/g/f475e1/32.png) [@gaspardelanuit](https://discourse.julialang.org/u/gaspardelanuit)\
**Post date:** [August 21, 2020, 2:11am UTC](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012/26 "2020-08-21T02:11:53Z")

</div>

Agreed. Transform with `Pipe.jl` really comes to life. I want to mention a new framework for some syntactic sugar around the basic transform/combine commands in DataFrame:  
[https://github.com/matthieugomez/DataFramesMacros.jl](https://github.com/matthieugomez/DataFramesMacros.jl)

Hope this is helpful to someone.

[Previous page](https://discourse.julialang.org/t/juliadb-dataframes-speculations-over-the-future-of-data-packages/14012.md?page=1)