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
Thanks for politely phrasing it as a question, but no this is an accidental change. I screwed up. The downstream libraries pretty much prevent INVALID HANDLES by design, how on earth did you find this? Luckily it should not be to hard to write a test for this to prevent that error in the future.
In pr #27 SqlReturn changed
SQL_INVALID_HANDLE = -2,
to
pub const INVALID_HANDLE: SqlReturn = SqlReturn(-1);
Is this correct?
The text was updated successfully, but these errors were encountered: