Thanks, Ryan, for working through this with me.
In response to your questions, (1) my connection string does not have any
non-ASCII characters, and it does not have any backslashes (nor does it need
any), and (2) yes, I’ve been using Racket CS. Here is the output from Racket BC:
Allocating env
So, it seems that there are two problems: (1) the connection fails (even
though it works with pyodbc) and (2) retrieving the diagnostic information
after the error hangs with the MS driver. I don't see an obvious reason for
either problem, but I have two thoughts.
Does your connection string have
Hi Ryan, thanks so much for your suggestions. Here is the output from running
your program with my original connection string, which works in python using
pyodbc:
Allocating env handle... done: 0
0
Setting ODBC version... done: 0
0
Allocating db handle... done: 0
0
Connecting... done: -1
This
The last time I tested connecting to MS SQL Server on Windows (several
years ago), I think I was able to connect using some drivers but not
others. I was simultaneously trying to figure out authentication and the
connection string format, so once I got a working configuration I stopped
Does anyone have experience using Racket to query a MS SQL Server? I'm
attempting to use the db-lib package (https://docs.racket-lang.org/db/) and
odbc-driver-connect, but running the method just hangs, with no feedback.
By contrast, using the same connection string, I can successfully connect
5 matches
Mail list logo
