In the case where both a connection string and a multiplexer are provided, the multiplexer is now preferred and no connection will be made. There is a strange edge case if a user reads the multiplexer property before setting it (in that case a connection is made), but I think it is not an issue in practice.
Fixes #19.
In the case where both a connection string and a multiplexer are provided, the multiplexer is now preferred and no connection will be made. There is a strange edge case if a user reads the multiplexer property before setting it (in that case a connection is made), but I think it is not an issue in practice.