allow using unix domain socket paths in connection form -> server field #438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
allow empty server valued in the connection form for postgres connections
add unix socket support for mariadb/mysql
refs: #437
test cases:
postgres connections should allow hostnames, IP addresses, empty values and absolute unix paths
mysql/mariadb connections should allow hostnames, IP addresses and absolute unix paths
postgres connections should look for sockets under default postgres socket path if server field is empty
postgres connections should look for sockets under the base path provided in the server field
mariadb/mysql connections should look for socket file specified by absolute socket path
other connection types: shoud work as before, file paths or empty values are not allowed
postgres/maridadb/mysql should work with ips and hostnames as before