The core of it is Rust: > Very fast kernels for SQL primitives like joins, filtering and aggregations. Quokka uses Polars to implement these. (I sponsor Polars on Github and you should too.) I am also exploring DuckDB, but I have found Polars to be faster so far.
I wrote a SQL engine in Python
31–40 of 81 posts
Re: I wrote a SQL engine in Python
#32I haven't looked into this in detail, and it seems like a fine project at a glance, but this caught my attention from the introduction: > When I set out, I had several objectives: > Easy to install and run, especially for distributed deployments. > [...] > The first two objectives strongly scream Python as the language of choice for Quokka. Python is probably one of the last languages I'd consider if ease of deployme…
Re: I wrote a SQL engine in Python
#33I haven't looked into this in detail, and it seems like a fine project at a glance, but this caught my attention from the introduction: > When I set out, I had several objectives: > Easy to install and run, especially for distributed deployments. > [...] > The first two objectives strongly scream Python as the language of choice for Quokka. Python is probably one of the last languages I'd consider if ease of deployme…
Re: I wrote a SQL engine in Python
#34The core of it is Rust: > Very fast kernels for SQL primitives like joins, filtering and aggregations. Quokka uses Polars to implement these. (I sponsor Polars on Github and you should too.) I am also exploring DuckDB, but I have found Polars to be faster so far.
that's certainly one way to look at it
Re: I wrote a SQL engine in Python
#35The core of it is Rust: > Very fast kernels for SQL primitives like joins, filtering and aggregations. Quokka uses Polars to implement these. (I sponsor Polars on Github and you should too.) I am also exploring DuckDB, but I have found Polars to be faster so far.
Re: I wrote a SQL engine in Python
#36Earlier quoted context omitted.
Perhaps you can write the underlying query engine :-) in something that's not Python lol
Even the self driving in Tesla use Python. If your Python is slow, you are using Python wrong. So it’s kind of a good thing that it’s natively slow, because you are not supposed to do your computations with native Python. It it was faster (added a lot of type hints and build processes), you would probably not be nudged in the right direction. https://cerfacs.fr/coop/fortran-vs-python
Re: I wrote a SQL engine in Python
#37Re: I wrote a SQL engine in Python
#38Earlier quoted context omitted.
that's certainly one way to look at it
Am I incorrect? Elsewhere in the thread you say this project is pure Python and then in the post you say you use a Rust library for queries. Am I misunderstanding something?
Is python-non-purity something that taints all dependants for you?
Re: I wrote a SQL engine in Python
#39Earlier quoted context omitted.
that's certainly one way to look at it
Am I incorrect? Elsewhere in the thread you say this project is pure Python and then in the post you say you use a Rust library for queries. Am I misunderstanding something?
I agree that saying “only” python gives an inaccurate implication, but it seems non-malicious and strictly correct. I don’t think they are trying to be misleading.
Re: I wrote a SQL engine in Python
#40Earlier quoted context omitted.
Am I incorrect? Elsewhere in the thread you say this project is pure Python and then in the post you say you use a Rust library for queries. Am I misunderstanding something?
Can't a pure Python project use any library that's not a pure Python project? Is python-non-purity something that taints all dependants for you?