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 recently tried out package sqlitemigration and found that it meant I had to change a bunch of places that were using *sqlitex.Pool. I'd like it if there was a pre-existing interface I could pass around that covered both of them.
And/or if I could have a method on sqlitemigration.Pool that returned a *sqlitex.Pool, perhaps eagerly running the migrations (I don't really need the laziness). that would make it a lot easier to retrofit into an existing project.
The text was updated successfully, but these errors were encountered:
In fact...I'm not sure I understand how this is meant to be used. In particular, why is it lazy? I kind of just want to do the migrations eagerly, know they worked, and then move on.
I recently tried out package sqlitemigration and found that it meant I had to change a bunch of places that were using
*sqlitex.Pool
. I'd like it if there was a pre-existing interface I could pass around that covered both of them.And/or if I could have a method on
sqlitemigration.Pool
that returned a*sqlitex.Pool
, perhaps eagerly running the migrations (I don't really need the laziness). that would make it a lot easier to retrofit into an existing project.The text was updated successfully, but these errors were encountered: