ibis VS store

ibis – portable Python dataframe library

The main benefit is that you get a Python (or R, Julia or Rust) interpreter. So you can evaluate code. A good example of the value of this is the Ibis docs which use Quarto: https://ibis-project.org/

Ive found polars quite intuitive, though for python, I lean more towards [ibis](https://ibis-project.org/). The interface is nearly identical, but ibis has the benefit if building sql queries before pulling any actual data (like dbplyr) — whereas polars requires the data to be in-memory (at least for rdb’s, though correct me if Im wrong)

this to me seems like a good argument for only using ibis, but Im happy to be convinced otherwise

Please add Ibis Birdbrain https://ibis-project.github.io/ibis-birdbrain/ to the list. Birdbrain is an AI-powered data bot, built on Ibis and Marvin, supporting more than 18 database backends.

See https://github.com/ibis-project/ibis and https://ibis-project.org for more details.

Ibis: The portable Python dataframe library

Cool! I do this, but I haven't seen anyone else do it. Is any of your code public?

I wrote about it at https://sive.rs/pg

and posted my SQL shopping cart at https://github.com/sivers/store

Please contact me if you'd like to share tips: https://sive.rs/contact

Also:

https://sive.rs/pg2 - Simplify: move code into database functions

https://sive.rs/pg - PostgreSQL example of self-contained stored procedures

some linked examples: https://github.com/sivers/store/tree/master/store/functions

I like this idea in theory ... although it would cause me to need to know a lot more SQL, which is a powerful but hostile language :-/

I care about factoring stuff out into expressions / functions and SQL fails in that regard ...

https://www.scattered-thoughts.net/writing/against-sql/

It's hard to imagine doing this with a ton of duplication. I have written SQL by hand and there are probably more confusing corners than shell, which is saying a lot (and which I didn't have too hard a time learning)