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
From the comments you added support for MSSQL in 2019 and init does indeed recognise connection strings such as:
sqlsrv://user:pass@server/db
However whenever I try and spin up the container, I get the following error:
In SQLSrvException.php line 57:
SQLSTATE [IMSSP, -8]: An invalid connection option key type was received. Option key types must be strings.
I have tried various combinations of connection string such as:
sqlsrv://user:pass@server\db
sqlsrv://user:pass@server\\db
sqlsrv://user:pass@server:port/db
sqlsrv://user:{pass}@server/db
and also variations of
sqlsrv://server/db;username=user;password=pass;
But I keep getting the same error.
Please can you add an example for sql server to the README.md ?
The text was updated successfully, but these errors were encountered:
As pointed out by @AdvanceGeneric in another issue (if only I had read it 2 days ago), the format mssql://user:pass@server:port/db does allow a connection, but it also comes up with "Unknown database type timestamp requested, Doctrine\DBAL\Platforms\SQLServer2012Platform may not support it." so I am not much further forward.
From the comments you added support for MSSQL in 2019 and init does indeed recognise connection strings such as:
sqlsrv://user:pass@server/db
However whenever I try and spin up the container, I get the following error:
In SQLSrvException.php line 57:
SQLSTATE [IMSSP, -8]: An invalid connection option key type was received. Option key types must be strings.
I have tried various combinations of connection string such as:
sqlsrv://user:pass@server\db
sqlsrv://user:pass@server\\db
sqlsrv://user:pass@server:port/db
sqlsrv://user:{pass}@server/db
and also variations of
sqlsrv://server/db;username=user;password=pass;
But I keep getting the same error.
Please can you add an example for sql server to the README.md ?
The text was updated successfully, but these errors were encountered: