You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need this in many cases, especially when working with Google's databases and developer tools, sockets can be quite common.
The Socket implementation in SQLx should not be PostgreSQL-specific as it is right now. Also the socket should be specified by the user, it can be different depending on the environment. For example GCP creates a socket bridge to the disk, which is not the default location found from your normal PostgreSQL installation.
The connection string in MySQL when using a socket should be:
We need this in many cases, especially when working with Google's databases and developer tools, sockets can be quite common.
The
Socket
implementation in SQLx should not be PostgreSQL-specific as it is right now. Also the socket should be specified by the user, it can be different depending on the environment. For example GCP creates a socket bridge to the disk, which is not the default location found from your normal PostgreSQL installation.The connection string in MySQL when using a socket should be:
Then again PostgreSQL has following format for UDS:
So this issue would require changes for a few things:
The text was updated successfully, but these errors were encountered: