2 ms·
The advantage of the intermediate step, I believe, is that you get everything in sql for free, without the need to re-implement. From the framequery docs: The
by goyglcgbbb 10y ago
The advantage of the intermediate step, I believe, is that you get everything in sql for free, without the need to re-implement. From the framequery docs:
The following limitations do exist: no support for non-numeric expressions, no support for outer joins with inequality conditions...and many, many more, SQL is crazy complex. The topics listed explicitly, however, are on the agenda to be fixed.
- chpr 10y agoAs the author of framequery: I agree that interpreting SQL on-top of pandas adds additional complexity. However, I belief it also has some benefits: Certainly, it should be more performant by side-stepping serialization and deserialization: "SELECT a + b FROM df " has only minimal overhead compared to "df['a'] + df['b']". It also offers the possibility to interpret queries on different dataframe implementations. Currently, I'm looking into implementing a dask executor (https://github.com/chmp/framequery/tree/feature/FQ-5-add-dask-support https://github.com/chmp/framequery/tree/feature/FQ-5-add-das...). Finally, I also feel as if "everything in sql" is a bit of stretch: sqlite has its limits, as does framequery. If there is anything in particular, that you are missing, please, feel free to open a GH issue. I would love feedback. As an aside, framequey is a mere month old and developed in my spare time, the limitations you cited reflect my current priorities and are, as written, planned to be fixed.