I've started to play a bit around trying to prototype a primitive async database interface.
There are several hard constrains for making such interface usable in diesel:
I've put together a small playground demonstrating that use case. To shorten that story: I'm not able to find an way to make that compiling. I think the first step towards an async database interface is to find a way to fix that.
@weiznich I'm not sure how useful this really is, but that interface is ~possible
That's certainly a step into the right direction, but without closures such an interface would be quite wired to work with.
Yeah, unfortunately async closures have a lot of issues still (I wasn’t able to get the HRTB bounds there to line up with them, that’s why I had to switch it out for a function)
Hello all! Definitely stoked that we have a database WG now! I've been doing a lot of work with the mongo driver, and built and the Wither project (an ODM) on top of it for model driven interaction with the database.
Definitely lots of additional work to be done, and the MongoDB team is apparently considering building a new one which will be maintained by the company and such. Who knows how long that will take, or if it will even happen. So I wanted to see if there is any interest in forking the current repo for the WG to maintain (which I would love to be a part of).
Essentially I was wanting to refactor the current lib to give it an async foundation (on top of tokio), and then finish building out its missing features. After that, the Wither project can be updated to support the async interface.
Let me know if you have any thoughts or are interested in this idea.