Things that are in our roadmap in relation to our data vision:

* Data management within your notebook (https://github.com/livebook-dev/livebook/issues/1604) - we want you to be able to link files, urls, and object storages to your notebook and automatically manage/download it

* We want to make it easier to build visualizations (even easier than the current Chart smart cell) and also be able to filter a dataframe by selecting a visualization: https://github.com/livebook-dev/livebook/issues/1545

We have other ideas, such as making SQL a more prominent citizen in Livebook and be able to build a custom canvas as your work on your notebook, but those will likely take longer to realize.

A vote here for a SQL cell. I want folks to use Livebook and Explorer more, but a very easy win for data folks who are not familiar with Ecto and are mostly writing complex select statements would be a sql code block that can easily reference a connection.

That would let people who are getting into Elixir for data work run a query, get an Explorer.DataFrame, and interact further that way.

Today we already have the SQL smart cell that works on a connection. But it is isolated from the data frame world. We hope to find ways to better integrate these two. :)

Good feedback, thanks.

Livebook already has a SQL Smart cell (https://livebook.dev/integrations/sql). It doesn't integrate with Explorer yet, but it's already possible to reference a database connection, run a SQL query, and visualize the results in a table.

Here's a video showing how to do that https://www.youtube.com/watch?v=F98OWdigCjY

We use the excellent Rustler Precompiled [1] library now so prebuilt binaries ship with the Elixir package. No Rust toolchain needed. :)

[1] https://github.com/philss/rustler_precompiled