Use Stream<Row> in API

[andygrove]

No description provided.

[sd2k]

@andygrove I tried to use a bunch of associated types on the various traits and managed to get the trait part to compile, although I haven't actually tried implementing the trait on the various database structs yet. I'm not sure if it's what you decided on in the end (following the chat in Discord) but maybe it's useful! sd2k@2adb34a

[andygrove]

@sd2k This is awesome :-) I was hoping someone would jump in and show me the way ... I think I chose the wrong database drivers to integrate with so we should perhaps look at tokio-postgres as the first one to implement with these new traits?

[sd2k]

Just taking a look at tokio-postgres. It immediately requires a change to the traits to make Driver::connect async, since the tokio_postgres::connect is async. Alternatively we could make the driver block on the creation of the connection. I've not got much experience with this sort of thing, but my hunch is that Drivers aren't created and destroyed regularly, so that may be acceptable? Never mind, we need to spawn the connection into an ongoing runtime so the method will still need to be async!

[sd2k]

This appears to be close to compiling now: sd2k@a483a82. I can't figure out how to make the params in execute_query Send which is blocking at the minute. I had to resort to using an Arc<tokio_postgres::Client> rather than tying the lifetime of TokioPostgresStatement to that of the client, but it probably won't matter realistically!

[sd2k]

By some absolute miracle I got it to compile. Check the tests for rdbc-tokio-postgres for examples! There are an awful lot of unwraps in the tests due to the amount of optional/result types returned by the methods, but I'm not sure it's avoidable - they're all valid from what I can tell.

I haven't even touched the other databases and I'm not completely sure how they'll work with the async traits.

Latest commit is here: sd2k@0993910