When the nom-sql version is upgraded you start getting really weird errors if the distributary version you have cached uses an older nom-sql version (and it won't get upgraded through cargo build - think you have to blow out the cache).
Since we're pinning nom-sql anyway I guess we might as well pin distributary too and avoid the issue altogether?
When the nom-sql version is upgraded you start getting really weird errors if the distributary version you have cached uses an older nom-sql version (and it won't get upgraded through
cargo build
- think you have to blow out the cache).Since we're pinning nom-sql anyway I guess we might as well pin distributary too and avoid the issue altogether?