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've noticed the DateTime millisecond precision seems to be losing the thousandth of a second figure. If I create a param (for a stored sproc request), with type DateTime and set the value to be 2016-05-27 11:05:06.763 (as a JS Date object). The actual value present in sqlserver seems to be 2016-05-27 11:05:06.760.
I assume this has something to do with the 3 millisecond precision of DateTime ( .000, .003, or .007) however it shouldn't be rounding 003 to 000.
As a quick fix I've changed Math.floor to Math.roundsee commit on my fork which seems to work... however I'm no expert in this area and not 100% sure if it's the correct fix, so waiting on advice before PR'ing.
The text was updated successfully, but these errors were encountered:
I've noticed the DateTime millisecond precision seems to be losing the thousandth of a second figure. If I create a param (for a stored sproc request), with type DateTime and set the value to be 2016-05-27 11:05:06.763 (as a JS Date object). The actual value present in sqlserver seems to be 2016-05-27 11:05:06.760.
I've tracked it down to this code in data-type.js
I assume this has something to do with the 3 millisecond precision of DateTime ( .000, .003, or .007) however it shouldn't be rounding 003 to 000.
As a quick fix I've changed
Math.floor
toMath.round
see commit on my fork which seems to work... however I'm no expert in this area and not 100% sure if it's the correct fix, so waiting on advice before PR'ing.The text was updated successfully, but these errors were encountered: