Set a transaction isolation level for MySQL connections by timvaillancourt · Pull Request #1156

Set a transaction isolation level for MySQL connections by timvaillancourt · Pull Request #1156 · github/gh-ost

Related issue: #1155

Description

This PR resolves #1155 by defining a connection-level transaction isolation level when setting up new MySQL connections. I also moved connection params to a slice that's joined into a string later-on because the giant params string was getting pretty unreadable. I also moved cases of log.Fatalf with no tokens to log.Fatal 🧹

At this time REPEATABLE_READ is used as the isolation for all connections following a discussion here: #1155

In case this PR introduced Go code changes:

contributed code is using same conventions as original code
script/cibuild returns with no formatting errors, build errors or unit test errors.