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 am contemplating implementing support for sqlite and first thing I saw was that for blocking you use diesel, but for asynk you are using bb8.
If everything was using diesel, all we would have to do is changing the connection pool to a AnyConnect (diesel 2.1) and little types/SQL tweaks and we would be golden for sqlite and mysql sypport. But asynk is using bb8, which implies we need to refactor the whole asynk code to use diesel.
But before diving into this task I wanted to make sure you didn't hit any roadblocks that forced you into going the bb8 route for asynk, versus sticking with diesel.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Pretty much the title.
I am contemplating implementing support for sqlite and first thing I saw was that for blocking you use diesel, but for asynk you are using bb8.
If everything was using diesel, all we would have to do is changing the connection pool to a AnyConnect (diesel 2.1) and little types/SQL tweaks and we would be golden for sqlite and mysql sypport. But asynk is using bb8, which implies we need to refactor the whole asynk code to use diesel.
But before diving into this task I wanted to make sure you didn't hit any roadblocks that forced you into going the bb8 route for asynk, versus sticking with diesel.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions