Open gnotisauton opened 2 years ago
sixeyed
commented
2 years ago Confirmed still present in 1.37.1, reverting to 1.32.1 fixes it. There's nothing very helpful in the Dev Tools logs, but if you can point me in the right direction I'll be happy to debug the issue.
gnotisauton
commented
1 year ago I'm teaching again, so I checked for a resolution again. The bug is still present in v1.38
After a bit of digging, I expect there's small differences between Azure SQL DB and Microsoft SQL Server (e.g. a database user cannot list all databases on a server). Maybe Azure SQL DB needs its own adapter in sqlectron-db-core, or some error checking would need to be introduced to work around the differences :/.
I'd be happy to provide access to an Azure SQL DB instance for testing purposes. I'd gladly help in any other way as well, I'm just not at all proficient in TypeScript or Electron development, unfortunately.
ruffin--
commented
3 months ago @gnotisauton Any luck getting this to work outside of 1.32.1?
Hrm, not sure if it's an Apple Silicon issue, but 1.32.1 won't even open on my M1 MacBook Air.
gnotisauton
commented
3 months ago I've tried the newest version each time I taught (1.36 and 1.38 iirc and others), without success. My conclusion: broken after 1.32.1 and not getting fixed.
I'm planning on usung a different client for the next iteration on the course, or drop teaching SQL altogether (it's a mixed data analysis course, so I could focus on other tools).
Sent from Proton Mail for iOS
On Fri, Aug 30, 2024 at 20:26, Ruffin @.***(mailto:On Fri, Aug 30, 2024 at 20:26, Ruffin < wrote:
@.***(https://github.com/gnotisauton) Any luck getting this to work outside of 1.32.1?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
When adding a connection to an Azure database (MSSQL connector) and connecting using SQL login and SSL, I get the following error:
Error invoking remote method 'DB_CONNECT': TypeError: Cannot read property '1' of nullConnection is successful (confirming server address, port, SSL setting) because switching to a wrong password results in the appropriate login rejection message and failed login log entry on the SQL server; using the correct password generates the above message.
Database/Schema are correct. Changing them results in the appropriate login failure message.
This bug was not present in v1.32.1, was introduced in v1.33.0, and has persisted since. I have been able to reproduce this bug on macOS and Windows, haven't tested other OSes.