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
I'm not sure what's happening and I'm not sure how to debug this. I'm open to suggestions on how to gather the right data.
I'm connecting to Sybase 11.0.3.3 and thda/tds seems to handle the TDS protocol this server version is using just fine normally. However I have one particular query that causes it to behave oddly, sometimes returning no data and sometimes entering an infinite loop or crashing.
I've simplified the failing query to select convert(real, @@timeticks) x. It does not fail if I do convert(real, 1) or just do select @@timeticks. It does fail with converting other @@ variables to real though. It also doesn't fail if I do convert(float(5), @@timeticks) but does fail if I do convert(float(4) @@timeticks)
I noted "real" is handled as a single precision float, I wonder if the TDS protocol isn't actually sending a double-width float though? Or perhaps the single precision parsing is just not quite right?
The text was updated successfully, but these errors were encountered:
Thanks for reporting.
Could you please try to run the tests ?
It might help to pinpoint the issue.
As mentionned in the readme this library is only tested on 12.5 or later versions.
I'm not sure what's happening and I'm not sure how to debug this. I'm open to suggestions on how to gather the right data.
I'm connecting to Sybase 11.0.3.3 and thda/tds seems to handle the TDS protocol this server version is using just fine normally. However I have one particular query that causes it to behave oddly, sometimes returning no data and sometimes entering an infinite loop or crashing.
I've simplified the failing query to
select convert(real, @@timeticks) x
. It does not fail if I doconvert(real, 1)
or just doselect @@timeticks
. It does fail with converting other @@ variables to real though. It also doesn't fail if I doconvert(float(5), @@timeticks)
but does fail if I doconvert(float(4) @@timeticks)
I noted "real" is handled as a single precision float, I wonder if the TDS protocol isn't actually sending a double-width float though? Or perhaps the single precision parsing is just not quite right?
The text was updated successfully, but these errors were encountered: