Previously, unless you jumped through some hoops, both sql.DB instances would be writable. It's not entirely clear that everything would work exactly as expected, but basic smoke tests for both DB's writing would work.
As of b22fb54, I think this may have changed. Some DoltEnv and MultiRepoEnv initialization code in Dolt changed. Tests in dependent repos had to be updated to not rely on multiple DB instances being writable simultaneously.
This was unintended, but it might be directionally where we're headed anyway. Regardless, we should investigate and write some tests before we cut a new driver release.
Previously, unless you jumped through some hoops, both sql.DB instances would be writable. It's not entirely clear that everything would work exactly as expected, but basic smoke tests for both DB's writing would work.
As of b22fb54, I think this may have changed. Some DoltEnv and MultiRepoEnv initialization code in Dolt changed. Tests in dependent repos had to be updated to not rely on multiple DB instances being writable simultaneously.
This was unintended, but it might be directionally where we're headed anyway. Regardless, we should investigate and write some tests before we cut a new driver release.