Closed thomas-reimonn closed 6 months ago
Resolves issue #58
It looks like duckdb isn't consistent about the ordering even when it's called the same way, I think that's going to cause bugs in peoples code.
I'd suggest that we order the results before returning them.
I also want to discuss scope of this a bit, but will continue that in #58
I'm going to merge this an open an issue to discuss ordering
This PR adds a
backend
(default: sqlite, optional: duckdb). Also it forces ordering by columns requested in order.Benchmarking:
Running tests using DuckDB backend pytest 40.40s user 7.76s system 196% cpu 24.544 total Running tests using Sqlite3 pytest 39.02s user 10.77s system 97% cpu 51.043 total
DuckDB is twice as fast because it used two cores, but about the same number of cpu cycles.