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
$ ODBC_TEST_CONNECTION_STRING='DRIVER={ODBC Driver 17 for SQL Server};SERVER=127.0.0.1;Uid=SA;Pwd=Passw0rd;Encrypt=no' cabal test -w ghc-9.2.7
…
1 of 1 test suites (1 of 1 test cases) passed.
however:
ODBC_TEST_CONNECTION_STRING='DRIVER={ODBC Driver 17 for SQL Server};SERVER=127.0.0.1;Uid=SA;Pwd=Passw0rd;Encrypt=no' cabal test -w ghc-9.4.5
…snip…
test/Main.hs:103:3:
1) Database.ODBC.Internal, Regression tests, Internal.exec can return SQL_NO_DATA
uncaught exception: ODBCException
UnsuccessfulReturnCode "odbc_SQLExecDirectW" (-1) "[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near '\8262'." (Just "42000")
To rerun use: --match "/Database.ODBC.Internal/Regression tests/Internal.exec can return SQL_NO_DATA/"
test/Main.hs:110:3:
2) Database.ODBC.Internal, Regression tests, Internal.exec multiple statements (https://github.com/fpco/odbc/issues/9)
uncaught exception: ODBCException
UnsuccessfulReturnCode "odbc_SQLExecDirectW" (-1) "[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near '\8251'." (Just "42000")
To rerun use: --match "/Database.ODBC.Internal/Regression tests/Internal.exec multiple statements (https://github.com/fpco/odbc/issues/9)/"
…snip…
100 examples, 47 failures, 44 pending
there certainly needs to be a special case for text v2 here, but simply removing the * 2 did not fix the bug
On current Master branch:
however:
there certainly needs to be a special case for text v2 here, but simply removing the
* 2
did not fix the bughaskell/text#365
The text was updated successfully, but these errors were encountered: