I have found these related issues/pull requests
Relates to #4187, #4212 and #4281
Description
Currently there is no way to provide custom transport for connecting to Postgres or MySql servers using sqlx. This means if you are unable to connect over TCP, you need to use an alternative library.
Prefered solution
The preferred solution would be to support AsyncRead + AsyncWrite transport inputs (or equivalent) so any transport provider can be used. This will unblock users in restricted environments, or testing with libraries such as turmoil that use custom TCP.
Is this a breaking change? Why or why not?
No this should be purely an additive feature
I have found these related issues/pull requests
Relates to #4187, #4212 and #4281
Description
Currently there is no way to provide custom transport for connecting to Postgres or MySql servers using sqlx. This means if you are unable to connect over TCP, you need to use an alternative library.
Prefered solution
The preferred solution would be to support
AsyncRead+AsyncWritetransport inputs (or equivalent) so any transport provider can be used. This will unblock users in restricted environments, or testing with libraries such asturmoilthat use custom TCP.Is this a breaking change? Why or why not?
No this should be purely an additive feature