Mathieu Borderé
Mathieu Borderé
Thanks that's interesting information. ~~As it's a duplicate of https://github.com/canonical/go-dqlite/issues/141, I will close this, but I'll have a look at it. Feel free to add extra information though, I'll see...
I more or less have an idea what's happening. Statements like `ExecContext(ctx, "INSERT INTO test (value) VALUES (?) RETURNING *", i)` will not work because an `Exec` is not expected...
It also looks like `RETURNING` is only supported in SQLite since version 3.35.0 (2021-03-12). libsqlite3 on Ubuntu Bionic Beaver https://launchpad.net/ubuntu/bionic/amd64/libsqlite3-dev/3.22.0-1 and Focal Fossa https://launchpad.net/ubuntu/focal/amd64/libsqlite3-dev/3.31.1-4 both don't support it. What do...
I would expect https://github.com/canonical/go-dqlite/pull/170 and https://github.com/canonical/go-dqlite/pull/168 to help a lot in that case too, especially the first one.
I think it has to do with the tls implementation in older go versions, can you (if you have time) experiment with go version 1.17 and see if you see...
Thanks for testing, always valuable! I'll have a look.
> Maybe I'm missing something -- if we're adding a version field to `raft_uv_transport` to prepare for evolving it in the future, why don't we also add a `reserved` field...
I'm working on the dqlite disk-mode in parallel, I'm currently figuring out a decent proposal for the snapshot mechanism, and analyze if anything needs to be added to this PR...
Looks pretty bad indeed.
Could be a variant of https://github.com/canonical/raft/pull/255