Hi! Not exactly an issue but a feature request.
I started using this sequelize dialect and after a while I figured that not every MS Sql Server installation is the same, so I can' t really rely on a standarized configuration (for my app). So the only thing I can trust is using a Windows x64 ODBC connection, connection via it' s DSN.
Current code in the Connection class makes some adjustments to the connectionString so it takes the SQL Server specific format, using the SQL Server Native Client, the SQL Native Client or the SQL Server driver, but no option to use the DSN of an ODBC connection.
A boolean useDSN could be an option, or checking if there's a dsn/DSN setting in the config object or the connectionString, so the constructor skips the actual driver detection.
Hope you consider this feature.
Best regards,
Jose Ignacio
redevill
commented
4 years ago
Hi! Not exactly an issue but a feature request. I started using this sequelize dialect and after a while I figured that not every MS Sql Server installation is the same, so I can' t really rely on a standarized configuration (for my app). So the only thing I can trust is using a Windows x64 ODBC connection, connection via it' s DSN.
Current code in the Connection class makes some adjustments to the connectionString so it takes the SQL Server specific format, using the SQL Server Native Client, the SQL Native Client or the SQL Server driver, but no option to use the DSN of an ODBC connection. A boolean useDSN could be an option, or checking if there's a dsn/DSN setting in the config object or the connectionString, so the constructor skips the actual driver detection.
Hope you consider this feature. Best regards, Jose Ignacio