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
That's some internal error "uh oh, something's wrong ... print out some
hints to help people debug!" message.
It looks like that's been fixed since, however as I don't see it in git
build.
Robby
On Sat, Sep 19, 2020 at 5:31 PM Kevin Forchione wrote:
> Hi guys.
>
> Using Racket 7.8 [cs[, If I
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
I don't have any good hints but the reader supplies span information that
can be used to disambiguate the original versions of some things (notably
"#t" vs "#true"). I doubt this is enough for numbers in any general sense
but following the path of actually carrying more information from the
reader
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
5 matches
Mail list logo