You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm asking this question because the deadpool-diesel implementation exposes deadpool_diesel::postgres::Pool which is set to PgConnection. The diesel-tracing library wraps the PgConnection struct into a InstrumentedPgConnection, which makes me thing using both is incompatible.
That said, I remember using r2d2 long ago and having kind of a generic interface instead of a concrete one, so I could replace the connection. This made me thing that maybe I'm missing something and I could use these two libs together. Can someone shed some light on my confusion?
The text was updated successfully, but these errors were encountered:
I'm asking this question because the deadpool-diesel implementation exposes
deadpool_diesel::postgres::Pool
which is set toPgConnection
. The diesel-tracing library wraps thePgConnection
struct into aInstrumentedPgConnection
, which makes me thing using both is incompatible.That said, I remember using r2d2 long ago and having kind of a generic interface instead of a concrete one, so I could replace the connection. This made me thing that maybe I'm missing something and I could use these two libs together. Can someone shed some light on my confusion?
The text was updated successfully, but these errors were encountered: