Pekka Enberg
Pekka Enberg
@rajivharlalka Yes, correct, that's the one.
@tryzniak Thanks, yes indeed. Looks like when the stale bot went crazy, I accidentally re-opened this.
Hey @jatin510, feel free, although I think it's more rewarding to do this when we support writes (#45) because then you can actually do something in-memory.
There is now experimental write path as of 01ec5f5e6472e0b7f752e1a3e47e560a19f34c42 so now an in-memory I/O is something that makes more sense. Probably needs `CREATE TABLE` support (#146) first to be useful.
We have in-memory mode. It could be improved, but that deserves a new issue.
I started the effort in https://github.com/tursodatabase/turso/pull/1980
I configured `cargo-dist` for the executable in 06c203425004100aa129d80227a2018509393234, but still need to find a way to do that for the static library.
After pull request #176, CPython no builds. The next step is to make it actually work: ``` penberg@turing:~/src/penberg/cpython$ ./python Python 3.14.0a0 (heads/main:e8c91d9, Jul 17 2024, 13:04:45) [GCC 13.2.1 20231205 (Red...
@lietu Right, the main reason to do CPython support like this is more about ensuring SQLite compatibility. A `pylimbo` package makes sense when we have some more of the functionality...
This still happens as of e1c8c676ca21490ec36ff13fb921db808861cd00 ``` sqlite> SELECT "limbo"; limbo sqlite> SELECT length("limbo"); 5 limbo> SELECT "limbo"; × Parse error: Column "limbo" not found limbo> SELECT length("limbo"); × Parse...