Now, we could fork tokio_postgres to our own set of crates, release them to crates.io and cut a release. But that would kind of be horrible idea for maintaining.
The other idea is to complete the SQLx transition (https://github.com/prisma/quaint/issues/138) and related tasks that triggered bugs with certain Postgres types in our quite dynamic setup. This needs some work on their side too.
Sigh, this is kind of a tough one. But it would be great to be able to finally cut a release to crates.io. What's stopping us?
Now, we could fork tokio_postgres to our own set of crates, release them to crates.io and cut a release. But that would kind of be horrible idea for maintaining.
The other idea is to complete the SQLx transition (https://github.com/prisma/quaint/issues/138) and related tasks that triggered bugs with certain Postgres types in our quite dynamic setup. This needs some work on their side too.